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

Update TODO

Browse source
This commit is contained in:
Joakim Frostegård 2020-08-03 05:15:48 +02:00
parent 9f445c7c03
commit 7733ee98ca
1 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

10
TODO.md
View file

@ -6,11 +6,11 @@
## aquatic_http_load_test ## aquatic_http_load_test
* opening new connections in current form causes macOS issues, why? * multiple workers is broken
* 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 enabled), then converting them to mio tcp streams
* really break and remove connection when reading 0 bytes? * really break and remove connection when reading 0 bytes?
* find out how to fully load opentracker * think about how to fully load opentracker. maybe keepalive can be activated
* Don't send keepalive header, it is not necessary with HTTP/1.1? (But * Don't send keepalive header, it is not necessary with HTTP/1.1? (But
opentracker might want it) opentracker might want it)
@ -43,6 +43,12 @@
* optimize serialize_20_bytes (10% cpu utilization). deserialize_20_bytes * optimize serialize_20_bytes (10% cpu utilization). deserialize_20_bytes
doesn't seem to be that expensive (1-2% cpu) doesn't seem to be that expensive (1-2% cpu)
## aquatic_ws_load_test
* there are probably many failures when running against wt-tracker causing
removal of connections and for that reason bad performance. likely reason
is different peer_id on same connection
* why are so few answers received?
## aquatic_udp ## aquatic_udp
* handle errors similarily to aquatic_ws, including errors in socket workers * handle errors similarily to aquatic_ws, including errors in socket workers
and using log crate and using log crate