On Thu, Jan 8, 2009 at 10:36 PM, Darryl Gove wrote:
> Ok. That's an entertaining problem. I'd suggest using the tools like
> mpstat, prstat to look at the activity of the system during the time
> when the fluctuations occur. You should also look at the dtrace toolkit
> since that covers a wide ran
Ok. That's an entertaining problem. I'd suggest using the tools like
mpstat, prstat to look at the activity of the system during the time
when the fluctuations occur. You should also look at the dtrace toolkit
since that covers a wide range of scenarios.
http://opensolaris.org/os/community/dtrac
On Fri, Jan 9, 2009 at 3:42 AM, Darryl Gove wrote:
> If you're looking at a single application, then I'd suggest trying the
> Performance Analyzer from Sun Studio. This should help you to see where the
> time is being spent. There's a timeline view which should help you identify
> what is happenin
If you're looking at a single application, then I'd suggest trying the
Performance Analyzer from Sun Studio. This should help you to see where
the time is being spent. There's a timeline view which should help you
identify what is happening during the fluctuations.
Regards,
Darryl.
S h i v w
On Tue, Jan 6, 2009 at 7:19 AM, S h i v wrote:
>
> Mapping the system level information that sar(1) has thrown into
> actual cause at process(or such) level has been the problem.
>
> Looking forward to get some insights.
>
On a side note, libgc.so (sun studio's garbage collection library) is
bein
