| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL as a local in-memory cache |
| Date: | 2010-06-17 19:59:39 |
| Message-ID: | 4C1A7EAB.3020202@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Josh Berkus wrote:
> a) Eliminate WAL logging entirely
> c) Turn off the background writer
Note that if you turn off full_page_writes and set
bgwriter_lru_maxpages=0, you'd get a substantial move in both these
directions without touching any code. Would help prove those as useful
directions to move toward or not. The difference in WAL writes just
after a checkpoint in particular, due to the full_page_writes behavior,
is a significant portion of total WAL activity on most systems.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre C | 2010-06-17 20:12:25 | Re: PostgreSQL as a local in-memory cache |
| Previous Message | Tom Lane | 2010-06-17 19:38:30 | Re: PostgreSQL as a local in-memory cache |