| From: | "Dmitry Koterov" <dmitry(at)koterov(dot)ru> |
|---|---|
| To: | |
| Cc: | "Joseph S" <jks(at)selectacast(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to speedup CHECKPOINTs? |
| Date: | 2007-03-29 20:13:41 |
| Message-ID: | d7df81620703291313u318c0ec2l218ab092c13ca18a@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
No, but disks are about 120 MB/s speed, peak writes during CHECKPOINT are
only 20-30 MB/s, and there is no disk read activity at all, so - no matter
where the xlog resides.
But now seems bgwriter tuning gets some effect, CHECKPOINT is running faster
(about 2-3 seconds instead of 10-15). It is still beats the performance, but
less.
On 3/29/07, CAJ CAJ <pguser(at)gmail(dot)com> wrote:
>
>
>
> On 3/28/07, Joseph S <jks(at)selectacast(dot)net> wrote:
> >
> > Dmitry Koterov wrote:
> >
> > > And the general question - why SELECT queries slowdown during the
> > > CHECKPOINT? I thought that Postgres is a version-based database and
> > read
> > > queries are never blocked...
> >
> > Because the disk is busy.
>
>
>
> Is your pg_xlog on a separate disk?
>
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2007-03-29 20:17:53 | Re: COPY command details |
| Previous Message | William Gray | 2007-03-29 19:58:14 | Re: Some encoding trouble via libpq |