We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I like to check performance from time to time (we should do it before merging all PRs).
I think the last time I run it was for this PR: #1091 (review)
Best case was:
Requests out: 492705.64/second Responses in: 415447.68/second - Connect responses: 205609.94 - Announce responses: 205718.08 - Scrape responses: 4119.67 - Error responses: 0.00 Peers per announce response: 0.00 Announce responses per info hash: - p10: 1 - p25: 1 - p50: 1 - p75: 1 - p90: 2 - p95: 3 - p99: 105 - p99.9: 331 - p100: 429
I have just run it (same machine):
Requests out: 349650.52/second Responses in: 341184.34/second - Connect responses: 168932.36 - Announce responses: 168850.59 - Scrape responses: 3401.39 - Error responses: 0.00 Peers per announce response: 0.00 Announce responses per info hash: - p10: 1 - p25: 1 - p50: 1 - p75: 1 - p90: 2 - p95: 3 - p99: 105 - p99.9: 277 - p100: 345
That's a −29,034601674% decrease.
cc @da2ce7
The text was updated successfully, but these errors were encountered:
Hi @da2ce7 I have executed the performance test with different commits (from more recent commits to oldest commits, after big changes):
http-protocol
primitives
The last one:
is the closest commit (I can compile with the current Rust version) to the commit that gave me the results above in the issue description:
Requests out: 492705.64/second
It does not give me the same result.
The machine is the same but other things have changed:
My plan is:
I'm closing this issue and I will open a new EPIC to review the performance. I think it makes sense to do it after finishing the stats overhaul.
Sorry, something went wrong.
No branches or pull requests
I like to check performance from time to time (we should do it before merging all PRs).
I think the last time I run it was for this PR: #1091 (review)
Best case was:
I have just run it (same machine):
That's a −29,034601674% decrease.
cc @da2ce7
The text was updated successfully, but these errors were encountered: