-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
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
Measure memory and file descriptor usage of ya-relay server under "heavy load" #191
Comments
M |
The proportion of different requests since September 1. until noon today is as follows: |
At an optimal number of connections (50), making discovery requests of the proportions described above, the relay reaches 170k responses/sec. This would be enough to sustain a network of over 3M nodes assuming the same average requests rate for connected nodes as now (approx 2.6 requests per minute). |
Blocked on #209. |
|
Reached 50k concurrently connected idle nodes. |
Load test run for up to 50k connections, weights find=1, neighbours=1, ping=8, 10 requests per connection and 25k req/s rate limit:
|
Average packet size for this setup during loading in 27.8 bytes, which shouldn't overflow a 32MiB buffers I've set via |
The typical response time grows ~linearly, and it appears that 50% of requests will time out at ~150k connections, assuming current load and no retransmissions. |
Detect any potential memory and file-descriptor leaks in the current implementation.
neighbours
- 6%,find_node
- 7%,ping
- 87%.Relevant investigation of ya-relay scaling: #215
The text was updated successfully, but these errors were encountered: