|
|
Re: OpenVZ cpu / mem monitor [message #6711 is a reply to message #6062] |
Thu, 21 September 2006 18:28 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
jason|xoxide
Messages: 20 Registered: September 2006 Location: Exton, PA
|
Junior Member |
|
|
I just downloaded your file and while it's a nice start, there seem to be a few bugs.
First off, the CPU usage doesn't work at all. It shows 100% idle no matter what is happening.
Next, free memory seems to be displaying KB, not MB (used RAM appear to be correct) and that makes the percentages break and always show 100% free.
Keep up the work though, as this will be a pretty useful app.
Jason Litka
http://www.jasonlitka.com
|
|
|
Re: OpenVZ cpu / mem monitor [message #6716 is a reply to message #6711] |
Thu, 21 September 2006 20:35 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
jasonaward
Messages: 9 Registered: September 2006
|
Junior Member |
|
|
The CPU usage was corrected sometime this afternoon. It should work correctly now.
As for the memory, it's working for everyone else who has tested it, but that doesn't mean it's working correctly for you. It's calculated based on your barrier in your /proc/user_beancounters file. it's based off of the first script found here:
http://wiki.vpslink.com/index.php?title=Memory_Utilization_S cript
If you are having issues with it, however, if possible, please post your user_beancounters file, and we can go from there (or at least the lines vmguar and privvm).
Thanks!
[Updated on: Thu, 21 September 2006 20:36] Report message to a moderator
|
|
|
Re: OpenVZ cpu / mem monitor [message #6718 is a reply to message #6062] |
Thu, 21 September 2006 20:48 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
jason|xoxide
Messages: 20 Registered: September 2006 Location: Exton, PA
|
Junior Member |
|
|
Well, that explains why the memory isn't working for me. I assumed that that figure was read from the systems physical memory and swap. I'm oversubscribing the server since I'm the only one who is using it. I know that all of the services aren't going to make me run out of memory and I'm too lazy to map out exactly what each VM is going to need. No matter, I know how much RAM+Swap I have so the current usage is really all I need to see.
As to the CPU usage, has the .c file in the first post been updated yet? If so, it's still not working for me as I just downloaded it again and recompiled. While building PHP in a VM, I see a steady 100% idle.
Jason Litka
http://www.jasonlitka.com
|
|
|
|
|
|
|
|
|
Re: OpenVZ cpu / mem monitor [message #7059 is a reply to message #6062] |
Mon, 02 October 2006 16:11 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
jason|xoxide
Messages: 20 Registered: September 2006 Location: Exton, PA
|
Junior Member |
|
|
Ok, I just downloaded and tried it again. It seems like the used memory reporting is broken as now it shows a steady 92.26MB used.
The CPU usage seems to work sometimes. For example, when building an RPM, I get a user percentage of 40-50. However, running an OPTIMIZE on a MySQL table shows 0% (even though top shows it as eating 100% of a single core).
Jason Litka
http://www.jasonlitka.com
|
|
|
|
Re: OpenVZ cpu / mem monitor [message #7996 is a reply to message #6062] |
Thu, 02 November 2006 15:45 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) |
jasonaward
Messages: 9 Registered: September 2006
|
Junior Member |
|
|
A couple of minor changes to th openvzmon tool.
1) Bug fix with debug file. File was be created (empty) even when the -o option wasn't given. This has been corrected.
2) Monitor now displays memory usage immediately upon execution. Before, it would wait until it had cpu statistics to report as well before displaying memory stats.
3) Added a new flag (-m) that, when provided, will only display the memory usage by the system and then immediately terminate. This is for the times when you need to know memory usage only and don't want the delay in cpu stat calculation or to be forced to terminate the application manually.
|
|
|