On 6/18/07, 陶捷 Euler Tao <[EMAIL PROTECTED]> wrote:
Dear all:
I'm compiling the ON build 65's source code now, using "nightly
opensolaris.sh" command.
The prstat reports that system is very idle, but the load average tells me
that the system is very busy. -,-
And then I check the vmstat report,
On 6/18/07, Wee Yeh Tan <[EMAIL PROTECTED]> wrote:
prstat may miss
Stupid safari3 is chopping off my post.
prstat may miss short lived processes and this seems possible because
you are compiling stuff.
--
Just me,
Wire ...
Blog:
___
opensolaris-di
On 6/18/07, 陶捷 Euler Tao <[EMAIL PROTECTED]> wrote:
ok, i see.
Then, how can I correct this problem when using prstat?
I'd try microstate accounting to see but I'm not sure if it will help.
You could also try to reduce the reporting interval.
Or is there any other statistics tool that could c
On 6/18/07, Jean-Francois Richard <[EMAIL PROTECTED]> wrote:
Typically, changing the prstat refresh time doesn't change
anything because the %cpu it is displaying remains the decaying average over
the last minute.
Jean,
You are certainly correct about pcpu. I was hoping that reducing
refresh
Hi
I don't know enough about the specifics for Open Solaris so the
following is based on the guess that it is the same as regular Solaris
(the fact that your vmstat r queue is at values like 7 and that idle CPU
is at 0% but prstat shows only about 4% CPU makes this feel like a good
guess) . Hist
Hi, Jean
Thank you for your explaination and your helpful advices :)
It seems you're right. After reading your guess, it reminded me that
something I've read from a book, Solairs Performance and Tools, and the
author talked about the decaying problem in this book.
2007/6/18, Jean-Francois Richa
ok, i see.
Then, how can I correct this problem when using prstat?
Or is there any other statistics tool that could catch these short lived
processes correctly?
2007/6/18, Wee Yeh Tan <[EMAIL PROTECTED]>:
On 6/18/07, Wee Yeh Tan <[EMAIL PROTECTED]> wrote:
> prstat may miss
Stupid safari3 is c
