Open iand opened 1 year ago
Things coming to mind:
(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.)
Thunderdome can be used for Kubo performance comparison. testground is an option too
We should create a separate issue for testing via Parsec since it doesn't use Kubo but is effectively a custom client using the accelerated DHT. This would be a good subtask of https://github.com/plprobelab/zikade/issues/20
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.