--- Andrew Sullivan <andrew@libertyrms.info> wrote:
> On Tue, Jan 14, 2003 at 09:50:04AM -0800, CaptainX0r wrote:
> > the G3. FWIW, top shows postgres slowly taking up all the
> CPU -
>
> Son't use top on Solaris 8. It's inaccurate, and it affects
> the results itself. Use prstat instead.
Thanks for the tip. Unfortunately it shows the same exact
thing.
> > This doesn't really tell me much, except I'm guessing that
> PG is
> > CPU bound?
>
> It looks that way. I've had iostat show CPU-bound, however,
> when the problem actually turned out to be memory contention.
> I think you may want to have a poke with vmstat, and also have
> a look at the SE toolkit.
I'll have a look at the SE toolkit - thanks.
vmstat shows me this:
# vmstat -s
0 swap ins
0 swap outs
0 pages swapped in
0 pages swapped out
125452 total address trans. faults taken
35245 page ins
60 page outs
194353 pages paged in
229 pages paged out
184621 total reclaims
184563 reclaims from free list
0 micro (hat) faults
125452 minor (as) faults
31764 major faults
10769 copy-on-write faults
80220 zero fill page faults
0 pages examined by the clock daemon
0 revolutions of the clock hand
170 pages freed by the clock daemon
601 forks
19 vforks
577 execs
370612 cpu context switches
1288431 device interrupts
148288 traps
1222653 system calls
294090 total name lookups (cache hits 48%)
43510 user cpu
4002 system cpu
480912 idle cpu
13805 wait cpu
procs memory page disk
faults cpu
r b w swap free re mf pi po fr de sr s6 sd -- -- in sy
cs us sy id
0 0 0 815496 538976 31 21 261 0 0 0 0 0 12 0 0 136 209
65 7 1 92
I've not much experience with this, it looks like there are
considerably more page ins than outs as compared to our other
solaris boxen but otherwise pretty normal.
-X
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com