Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'iPulse / top CPU usage' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
iPulse / top CPU usage
Authored by: Anonymous on Nov 25, '02 11:15:27AM

It is quite likely that iPulse displays the 'idle' CPU usage more as 'the CPU usage average as influenced by the moment of sampling'. Of course, sampling eats a bunch of CPU because the app is updating the UI and, as such, the CPU usage will be high.

Same reason why 'top' seems to eat 10% to 15% of the CPU even though it sleeps for 99/100s of a second.

Real world metrics show that neither app use as much CPU as they indicate. iPulse will certainly consume more than top simply because it (a) monitors more stuff and (b) gives graphical indication as to the status of the system in a fashion that uses transparency (a simple bar graph would use less CPU than top, most likely -- drawing a terminal window is expensive).



[ Reply to This | # ]
iPulse / top CPU usage
Authored by: derrickbass on Nov 27, '02 04:02:09PM

To what real world metrics do you refer? I ran top on my PB G4 500 using
time top
At the end, time reported that top spent 1.46 seconds in user mode and 8.61 seconds in kernel mode out of 1:15 of real time, for 13.3% utilization, which is pretty much top had reported about itself. My real world metric implies top really is a CPU hog.



[ Reply to This | # ]