The reply below is way too long, but oh well.
The summary is:
I am 100% certain that my ExprCount() loop is CPU bound. It is unfortunate
that time gives inaccurate information about this. It would be nice if the
documentation acknowledged that in order to save future generations from
confusion. I
Linda Walsh wrote:
>
> Bruce Dawson wrote:
>> How many CPUs do you have? 20% usage doesn't mean anything without knowing
>> that. On a five-core system 20% usage would imply one full core.
---
Another tool to check out if you have it is 'qps'... it can show the
time slice/schedule interval ... I
Bruce Dawson wrote:
> How many CPUs do you have? 20% usage doesn't mean anything without knowing
> that. On a five-core system 20% usage would imply one full core.
---
If you look at the example that shows no process spawning overhead,
it shows 100% cpu usage. 100%=1CPU, regardless of co
How many CPUs do you have? 20% usage doesn't mean anything without knowing
that. On a five-core system 20% usage would imply one full core.
> It's your kernel settings that are causing issue.
Hmmm? My kernel is correctly ensuring that there is no idle time. It is
switching instantly between bash
Bruce Dawson wrote:
> Hmmm -- again, that doesn't match what I see. bash is suspended while it
> waits for expr to run, and the instant that expr completes bash runs again.
> This can be seen in the profiler screenshot. The CPU is busy at all times,
> and always busy on exactly one process.
---
Hmmm -- again, that doesn't match what I see. bash is suspended while it
waits for expr to run, and the instant that expr completes bash runs again.
This can be seen in the profiler screenshot. The CPU is busy at all times,
and always busy on exactly one process.
The scheduler is invoked whenever
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
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 r
On Tue, Mar 19, 2013 at 5:03 AM, Bruce Dawson
wrote:
> I'll give those a try.
>
> BTW, I just posted the blog post to share what I'd found. You can see it
> here:
>
> http://randomascii.wordpress.com/2013/03/18/counting-to-ten-on-linux/
>
> I hope it's accurate, and I do think it would be worth me
