From: | henk de wit <henk53602(at)hotmail(dot)com> |
---|---|
To: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | When does sequential performance matter in PG? |
Date: | 2009-03-10 14:09:10 |
Message-ID: | COL104-W4301D2DDC445A99E55E086F5A10@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
It is frequently said that for PostgreSQL the number 1 thing to pay attention to when increasing performance is the amount of IOPS a storage system is capable of. Now I wonder if there is any situation in which sequential IO performance comes into play. E.g. perhaps during a tablescan on a non-fragmented table, or during a backup or restore?
The reason I'm asking is that we're building a storage array and for some reason are unable to
increase the number of random IOPS beyond a certain threshold when we add more controllers or more (SSD) disks to the system. However, the sequential performance keeps increasing when we do that.
Would this extra sequential performance be of any benefit to PG or would it just be wasted?
Kind regards
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Wakeling | 2009-03-10 14:28:07 | Re: When does sequential performance matter in PG? |
Previous Message | Guillaume Cottenceau | 2009-03-10 09:41:19 | Re: [PERFORM] Query much slower when run from postgres function |