Describing a performance problem.
Machine-translated from Russian. Show original
Technical support staff often get reports that mention performance problems and include some data analysis. That information isn't enough to pinpoint why performance has dropped.
A report may say the CPU is at 100 percent or that the run queue is very long, but those facts tell you nothing about what is causing the performance problem.
For example, users connect to a system over a network through several routers. They complain that the system is slow. The report data shows that the system's CPU is overloaded. But the real cause of the poor performance may be a delay in echoing characters to terminals because of packet loss on the network (due to congested networks and routers). So the source of the problem isn't necessarily tied to the system's CPU load. On the other hand, a batch job that takes too long to run does have a direct connection to the load on the CPU and the I/O subsystem.
Answering ideas 0
No ideas yet. Propose the first one.
Sign in — offer an idea
Discussion nothing yet
Sign in — to join the discussion