| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "jgardner(at)jonathangardner(dot)net" <jgardner(at)jonathangardner(dot)net> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL as a local in-memory cache |
| Date: | 2010-06-16 17:37:06 |
| Message-ID: | 1276709804-sup-438@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Excerpts from jgardner(at)jonathangardner(dot)net's message of mié jun 16 02:30:30 -0400 2010:
> NOTE: If I do one giant commit instead of lots of littler ones, I get
> much better speeds for the slower cases, but I never exceed 5,500
> which appears to be some kind of wall I can't break through.
>
> If there's anything else I should tinker with, I'm all ears.
increase wal_buffers?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-06-16 19:00:22 | Re: PostgreSQL as a local in-memory cache |
| Previous Message | Balkrishna Sharma | 2010-06-16 17:00:22 | Parallel queries for a web-application |performance testing |