One big caveat re. the "SAME" striping strategy, is that readahead can
really hurt an OLTP you.
Mind you, if you're going from a few disks to a caching array with many
disks, it'll be hard to not have a big improvement
But if you push the envelope of the array with a "SAME" configuration,
read
I'm confused why you say the system is 70% busy: the vmstat output
shows 70% *idle*.
The vmstat you sent shows good things and ambiguous things:
- si and so are zero, so your not paging/swapping. Thats always step
1. you're fine.
- bi and bo (physical IO) shows pretty high numbers for how many
it's very good to understand specific choke points you're trying to
address by upgrading so you dont get disappointed. Are you truly CPU
constrained, or is it memory footprint or IO thruput that makes you
want to upgrade?
IMO The best way to begin understanding system choke points is vmstat
o
unsubscribe
On Jan 27, 2004, at 3:20 PM, [EMAIL PROTECTED] wrote:
Message Digest
Volume 1 : Issue 1204 : "index" Format
Messages in this Issue:
200401/245: Re: Problems with pg_dump
200401/246: Error seen when vacuuming pg_largeobject table
200401/247: Re: Error seen when vacuuming pg_large
