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 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
On 9/24/07, Alex <[EMAIL PROTECTED]> wrote:
> Obviously prstat(1M) is a great interactive tool, but it's less
> useful to me to use for backgrounded logging since it doesn't have a
> time stamp and so forth. Is there a tool in Solaris 10 where I can
> monitor this useful statistic without having to
Hi!
When I run prstat(1M) with the -m option, I get a column called `LAT'. It has
been explained to me that this is interval latency between a process becoming
ready to run until it has been scheduled and allowed a time slice.
Obviously prstat(1M) is a great interactive tool, but it's less usef
