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

monitor CPU load on server #41

Open
aglyzov opened this issue Jun 22, 2012 · 7 comments
Open

monitor CPU load on server #41

aglyzov opened this issue Jun 22, 2012 · 7 comments

Comments

@aglyzov
Copy link
Contributor

aglyzov commented Jun 22, 2012

In addition to monitoring memory load we need to monitor CPU load.

@jlouis
Copy link
Contributor

jlouis commented Jun 22, 2012

That is indeed a nice idea. While at it, I suggest we monitor network throughput as well. The reason is that all of these 3 parameters, memory, CPU or Bandwidth will hurt a lot if they are limiting factors.

For instance, if you can saturate the network and run "as many conns as possible", then you are really measuring the size of headers in different systems. This means that we end up with the server which does the correct full headers being the loser of the test.

@ericmoritz
Copy link
Owner

Ok, I'll add those, it's pretty easy to add to server_manager.py

@ericmoritz
Copy link
Owner

Hey, not doing the correct thing does wonders for MongoDB benchmarks :p

@ericmoritz
Copy link
Owner

Do you have any idea how to measure bandwidth saturation?

@jlouis
Copy link
Contributor

jlouis commented Jun 26, 2012

Only on FreeBSD :/

@aglyzov
Copy link
Contributor Author

aglyzov commented Jun 26, 2012

How about this: http://www.frenchfries.net/paul/tcpstat/

(available in ubuntu)

@ericmoritz
Copy link
Owner

Here's a dump of netstat -s after a number of connection timeouts for the Java webbit server. Is there anything glaring that anyone sees?

https://gist.github.com/3019940

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants