Soak testing DKV for detecting memory leaks #5
Labels
good first issue
Good for newcomers
help wanted
Extra attention is needed
validation
Testing or benchmarking
Given that DKV contains significant functionality that makes it suitable for production use cases, we must execute soak/saturation testing on the current implementation to detect any memory leaks, CPU spikes or any other abnormal behaviour when left running for longer duration.
This issue captures this effort and any problems discovered in the process will be reported as separate issues within this project.
The text was updated successfully, but these errors were encountered: