From: | Andreas Forø Tollefsen <andreasft(at)gmail(dot)com> |
---|---|
To: | Kenneth Marshall <ktm(at)rice(dot)edu> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance issues |
Date: | 2011-03-07 14:29:40 |
Message-ID: | AANLkTim4RoKaQcBWhjer34a0EjSX-PWQkoXGYV0YY=kM@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Ok. Cheers. I will do some more testing on my heavy PostGIS queries which
often takes hours to complete.
Thanks.
Andreas
2011/3/7 Kenneth Marshall <ktm(at)rice(dot)edu>
> On Mon, Mar 07, 2011 at 03:17:05PM +0100, Andreas For? Tollefsen wrote:
> > Thanks, Ken.
> >
> > It seems like the tip to turn off synchronous_commit did the trick:
> >
> > /usr/lib/postgresql/8.4/bin/pgbench -T 60 test1
> > starting vacuum...end.
> > transaction type: TPC-B (sort of)
> > scaling factor: 1
> > query mode: simple
> > number of clients: 1
> > duration: 60 s
> > number of transactions actually processed: 86048
> > tps = 1434.123199 (including connections establishing)
> > tps = 1434.183362 (excluding connections establishing)
> >
> > Is this acceptable compared to others when considering my setup?
> >
> > Cheers,
> > Andreas
> >
>
>
> These are typical results for synchronous_commit off. The caveat
> is you must be able to handle loosing transactions if you have a
> database crash, but your database is still intact. This differs
> from turning fsync off in which a crash means you would need to
> restore from a backup.
>
> Cheers,
> Ken
>
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2011-03-07 15:34:35 | Re: Performance issues |
Previous Message | Kenneth Marshall | 2011-03-07 14:22:16 | Re: Performance issues |