Update TODO

This commit is contained in:
Joakim Frostegård 2020-04-12 22:07:11 +02:00
parent 06ff4ad9d0
commit 6c4013ca55

21
TODO.md
View file

@ -18,22 +18,29 @@
# Not important # Not important
## aquatic
* No overflow on instant + duration arithmetic now, hopefully? * No overflow on instant + duration arithmetic now, hopefully?
* extract_response_peers * extract_response_peers
* Cleaner code * Cleaner code
* Stack-allocated vector? * Stack-allocated vector?
* Benchmarks * Use log crate for errors, including logging thread names? I could probably
use code from old rs_news project for that.
* Performance
* cpu-target=native good?
* mialloc good?
* Use less bytes from PeerId for hashing? (If yes, only save half of them
or so in PeerMapKey). Might improve performance, but probably not worth
it.
## aquatic_bench
* num_rounds command line argument * num_rounds command line argument
* Send in connect reponse ids to other functions as integration test * Send in connect reponse ids to other functions as integration test
* Save last results, check if difference is significant? * Save last results, check if difference is significant?
* ProgressBar: `[{elapsed_precise}]` and eta_precise? * ProgressBar: `[{elapsed_precise}]` and eta_precise?
* Test server over udp socket instead? * Test server over udp socket instead?
* Performance
* cpu-target=native good? ## bittorrent_udp
* mialloc good?
* Use less bytes from PeerId for hashing? Would need to implement
"faulty" PartialEq too (on PeerMapKey, which would be OK)
* bittorrent_udp
* Avoid heap allocation in general if it can be avoided? * Avoid heap allocation in general if it can be avoided?
* request from bytes for scrape: use arrayvec with some max size for * request from bytes for scrape: use arrayvec with some max size for
torrents? With Vec, allocation takes quite a bit of CPU time torrents? With Vec, allocation takes quite a bit of CPU time