YGGverse/aquatic
1
0
Fork 0
mirror of https://github.com/YGGverse/aquatic.git synced 2026-04-02 02:35:31 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update TODO

Browse source
This commit is contained in:
Joakim Frostegård 2020-08-12 04:45:54 +02:00
parent 6f955235ea
commit 8c4d3e5cb9
1 changed files with 0 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
TODO.md
View file

@ -12,13 +12,11 @@
and in opentracker (when closing connections immediately in tracker) and in opentracker (when closing connections immediately in tracker)
* maybe check performance against other well-known implementations than * maybe check performance against other well-known implementations than
opentracker (which hopefully do keep-alive) opentracker (which hopefully do keep-alive)
* Don't send keepalive header, it is not necessary with HTTP/1.1
* try creating sockets with different ports (and also local ips if setting * try creating sockets with different ports (and also local ips if setting
enabled), then converting them to mio tcp streams? (so that so_reuseport enabled), then converting them to mio tcp streams? (so that so_reuseport
can distribute them to different workers) can distribute them to different workers)
## aquatic_http ## aquatic_http
* update tests for simd-json
* test torrent transfer with real clients * test torrent transfer with real clients
* test tls * test tls
* scrape: does it work (serialization etc), and with multiple hashes? * scrape: does it work (serialization etc), and with multiple hashes?
@ -26,12 +24,10 @@
positive number. positive number.
* compact=0 should result in error response * compact=0 should result in error response
* config: multiple request workers * config: multiple request workers
* actually delete old benchmark
## aquatic_ws_load_test ## aquatic_ws_load_test
* too many responses received with aquatic_ws? * too many responses received with aquatic_ws?
* wt-tracker: why lots of responses with no (new) requests? * wt-tracker: why lots of responses with no (new) requests?
* offers_per_request or similar config var
* count number of announce requests sent, total number of offers sent, * count number of announce requests sent, total number of offers sent,
and answers sent. compare these with responses received. same for and answers sent. compare these with responses received. same for
scrape requests I suppose. scrape requests I suppose.