Skip to content
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

Counters for low/high watermark state transititioning #5

Open
oberstet opened this issue Nov 2, 2013 · 0 comments
Open

Counters for low/high watermark state transititioning #5

oberstet opened this issue Nov 2, 2013 · 0 comments

Comments

@oberstet
Copy link
Contributor

oberstet commented Nov 2, 2013

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:

  • total number of transitions to high-watermark reached (pausing)
  • total number of transitions to low-watermark reached (resuming)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant