> > > I process that is started every 5 seconds and exits after 10ms > > computation can cause the load to go up by 1. It just matters if it runs > > during the sampling time or not. This is why the load avarage is not > > accurate, it is an indication and if the value is below the number of > CPUs > > you may well see quantization errors. > > > > So yes, maybe there is something going on but even top -s .1 -I will > have a > > hard time to show it to you. It may be too h interestingsmall of a blib > to spot. > > Ah, interesting. Any idea on how to measure/catch something like that? How > would one find such a process? >
If you have such a process (and see "load 1.0" in top) you don't have a load problem on this computer, so "finding" it becomes irrational. This means that you are chasing a symptom but where you lack an actual problem. If your cpu is busy 10ms every 5 seconds it is basically idle, and the small percentage you see is totally within measurement error margins. But load is a very bad measurement tool as previously stated in this thread. -- May the most significant bit of your life be positive.
