On Wed, May 21, 2008 at 08:11:30PM +0200, Zeljko Vrba wrote:
> On Wed, May 21, 2008 at 07:24:50PM +0200, Henrik Johansson wrote:
> >
> > Total idle time reported by vmstat is about 60-80% and mpstat shows
> > that no cpu(hwthread) is utilized to even near the 100%. I've also
> > seen that the
G'Day Rick,
On Mon, May 05, 2008 at 11:15:01AM -0500, rickey c weisner wrote:
> Greetings,
> I used the SE toolkit for years. I was particularly fond of
> nx.se. It was not unusual for me to have to add support
> for new NIcs.
>
> So I have written my own tool using C and the kstat api.
> It giv
G'Day Henrik,
On Wed, May 21, 2008 at 07:24:50PM +0200, Henrik Johansson wrote:
> Hello all,
>
> I a bit curious, what other factors that the availability of CPU-time
> can cause latency for processes scheduling?
>
> I have a few M5000 running 127111-10 with lots of CPU-cycles to spare,
> bu
On Wed, May 21, 2008 at 07:24:50PM +0200, Henrik Johansson wrote:
>
> Total idle time reported by vmstat is about 60-80% and mpstat shows
> that no cpu(hwthread) is utilized to even near the 100%. I've also
> seen that the run queue sometimes goes up to 2 while we still have
> lots of cpu-t
Hello all,
I a bit curious, what other factors that the availability of CPU-time
can cause latency for processes scheduling?
I have a few M5000 running 127111-10 with lots of CPU-cycles to spare,
but according to microstate accounting threads sometimes spend ~5-35%
of their time waiting to
