You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E.g. on one hand, there is I think a fundamental tradeoff between throughput and latency. Maximizing throughput would be simply done by overwhelming the server with so many outstanding WS connections that there is always stuff to process - up to a hard limit of course (like accept queue depth).
This will result in best throughput, but probably bad latencies for individual WS connections.
Then, for a server that can process incoming connections so fast that the high watermark is never reached (when operating in modes other than --close keepopen), it might be hard to find out the best value for high watermark (that is just below hard limit) even if I am only interested in throughput.
At least for me, I could find out more / understand better, if we had the following 2 counters in wsperf:
total number of transitions to high-watermark reached (pausing)
total number of transitions to low-watermark reached (resuming)
The text was updated successfully, but these errors were encountered:
I am still unsure how to best approach.
E.g. on one hand, there is I think a fundamental tradeoff between throughput and latency. Maximizing throughput would be simply done by overwhelming the server with so many outstanding WS connections that there is always stuff to process - up to a hard limit of course (like accept queue depth).
This will result in best throughput, but probably bad latencies for individual WS connections.
Then, for a server that can process incoming connections so fast that the high watermark is never reached (when operating in modes other than
--close keepopen
), it might be hard to find out the best value for high watermark (that is just below hard limit) even if I am only interested in throughput.At least for me, I could find out more / understand better, if we had the following 2 counters in
wsperf
:The text was updated successfully, but these errors were encountered: