So, how can I find out whats causing my sys time v.high?

"Patrick Begou" <Patrick.Begou@hmg.inpg.fr> wrote in message
news:ck0mh2$csu$1@news.grenet.fr...
> Riz wrote:
> > Here is the output from iostat -d 4
> > Disks: % tm_act Kbps tps
> > Kb_read Kb_wrtn
> >
> > hdisk5 0.0 0.0
0.0
> > 1784 1436
> >
> > hdisk3 0.3 5.5
0.9
> > 203802 603651
> >
> > hdisk4 0.0 0.0
0.0
> > 0 0
> >
> > hdisk2 0.4 5.2
1.0
> > 148531 603175
> >
> > hdisk1 0.0 0.0
0.0
> > 0 0
> >
> > hdisk6 0.0 0.0
0.0
> > 2296 1816
> >
> > hdisk0 7.8 514.0
37.2
> > 71408704 3603944
> >
> >
> > I think there is no extra ordinary disk activity. Here is the out put of
> > iostat.
>
> May be you should wait additional time (iostat is sampling every 4s in
> this case) to have more detailed informations. May be restrict the
> information to the DD where is located your database while it is in use
>
> iostat -d your_physical_volume 4
>
> and look at the values for several minutes (check with "vmstat 4" your
> system activity in parallel).
>
>
> But may be your sys time is not related to I/Os. But you must identify
> what is this sys time to solve your problem.