Hell, Robert wrote:
> > I tried different other tools for random IO (including a self
written one which does random lseek and read).
> >
> > This tool, started during one of our tests, achieves 2 iops (8k each).
> > Started alone I get something about 1,500 iops with an avg latency
of 100 ms.
1500 iops looks about right for 4x2 RAID 10 volume. What's your worst
latency (as reported by the tool)? iowait is mostly seek time.
> > We are using SAN (EMC CLARiiON CX 300) - are those ~7 MB/s really
our bottleneck?
Depending on your access pattern to the database, it could be (if you
have lots of random IO, and 180 concurrent database threads can make any
IO random enough). Are your queries read-mostly or a mix?
> > Any other tuning ideas?
Only generic ones:
- Are your queries optimized, use indexes, etc.?
- Try PostgreSQL 8.3 - if you have sequential seeks it can in theory
make better use of data between connections.
- Do you have enough memory dedicated to data caches, both in PostgreSQL
and in the OS? (i.e. what is your shared_buffers setting?)
- If the SAN can configure parameters such as prefetch (pre-read) and
stripe size, try lowering them (should help if you have random IO).
