I think you misunderstand...what Pierre is saying -- your process is scheduled out to give others a *chance* to run and the scheduler isn't called often enough to roll you back in immediately when it finds out that no one else needs their time ticks...
That's why I mentioned all of the scheduling info in the kernel. Another thing to play with is length of time slices, but I have a feeling as soon as you hit the eval you are yielding the cpu to the scheduler, so while you may be *waiting* 100% on the cpu, much of that is spent waiting for cpu, not using cpu. Bruce Dawson wrote: > Thanks Pierre. > > The profile results, especially the zoom profiler screen shot, show that > virtually all of the CPU time being consumed is from bash and its child > processes. The system is otherwise idle with no other processes running to > any significant degree. My system is ~99.5% idle when I'm not running the > test, and ~91.5% idle when the test is running. > -----Original Message----- > From: Pierre Gaston [mailto:pierre.gas...@gmail.com] > For what it's worth, I still thinks that time is not lying (though the man > page warns about possible inaccuracies), Your loop with expr might be "cpu > bound" but it does not run often because other processes are given a chance > to run. > >
