Comment by rbanffy

Comment by rbanffy 6 days ago

In the late 1990's I worked in a company that had a couple mainframes in their fleet and once I looked into a resource usage screen (Omegamon, perhaps? Is it that old?) and noticed the CPU was pegged at 100%. I asked the operator if that was normal. His answer was "Of course. We paid for that CPU, might as well use it". Funny though that mainframes are designed for that - most, if not all, non-application work is offloaded to other processors in the system so that the CPU can run applications as fast as it can.

defrost 6 days ago

Having a number of running processes take the CPU usage to 100% is one thing, have an under utilised CPU with almost no processes running report that usage is at 100% is another thing, the subject of the article here.

Reply View 3 replies

rbanffy 6 days ago

I didn't intend this as an example of the issue the article mentions (a misreporting of usage because of a hardware design issue). It was just a fun example of how different hardware behaves differently.
One can also say Omegamon (or whatever tool) was misreporting, because it didn't account for the processor time of the various supporting systems that dealt with peripheral operations. After all, they also paid for the disk controllers, disks, tape drives, terminal controllers and so on, so they could want to drive those to close to 100% as well.

Reply View | 1 reply
- defrost 6 days ago
  
  Sure, no drama - I came across as a little dry and clipped as I was clarifying on the fly as it were.
  I had my time squeezing the last cycle possible from a Cyber 205 waaaay back in the day.
  
  Reply View | 0 replies
datadrivenangel 6 days ago

Some mainframes have the ability to lock clock speed and always run at exactly 100%, so you can often have hard guarantees about program latency and performance.

Reply View | 0 replies