| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Laurent Laborde <kerdezixe(at)gmail(dot)com> |
| Cc: | Ivan Voras <ivoras(at)freebsd(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: limiting performance impact of wal archiving. |
| Date: | 2009-11-10 15:43:34 |
| Message-ID: | dcc563d10911100743j640c471cn78b5394dca2b5120@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Nov 10, 2009 at 8:00 AM, Laurent Laborde <kerdezixe(at)gmail(dot)com> wrote:
>
> Desktop drive can easily do 60MB/s in *sequential* read/write.
> We use high performance array of 15.000rpm SAS disk on an octocore
> 32GB and IO is always a problem.
How man drives in the array? Controller? RAID level?
> I explain the problem :
>
> This server (doing wal archiving) is the master node of the
> over-blog's server farm.
> hundreds of GB of data, tens of millions of articles and comments,
> millions of user, ...
> ~250 read/write sql requests per seconds for the master
> ~500 read sql request per slave.
That's really not very fast.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-11-10 15:48:35 | Re: limiting performance impact of wal archiving. |
| Previous Message | Laurent Laborde | 2009-11-10 15:37:45 | Re: limiting performance impact of wal archiving. |