Test Refactored DHT in Kubo
iand opened this issue · comments
Ian Davis commented
ETA: 2023-09-30
Description
Test the refactored DHT within Kubo, on MANY clients before deploying the DHT refactor to the next Kubo release.
The tests to be conducted must include testing that Content Routing still behaves as expected, but also performance evaluation and comparison with the legacy DHT implementation.
Steve Loeppky commented
Things coming to mind:
- I assume we'll use Thunderdome for some DHT client testing
- I assume we'll also test within Nebula and Parsec
(We should cover what we gain by testing in a given context. For example, I assume testing in Thunderdome serves as a catch-all for latency and resource validation.)