-
Notifications
You must be signed in to change notification settings - Fork 58
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
Comments
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. |
Ok, I'll add those, it's pretty easy to add to server_manager.py |
Hey, not doing the correct thing does wonders for MongoDB benchmarks :p |
Do you have any idea how to measure bandwidth saturation? |
Only on FreeBSD :/ |
How about this: http://www.frenchfries.net/paul/tcpstat/ (available in ubuntu) |
Here's a dump of |
In addition to monitoring memory load we need to monitor CPU load.
The text was updated successfully, but these errors were encountered: