Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PostgreSQL as a local in-memory cache
- 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: Thu, 17 Jun 2010 15:59:39 -0400
- Message-id: <4C1A7EAB.3020202@2ndquadrant.com> <text/plain>
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
- References:
- PostgreSQL as a local in-memory cache
- From: jgardner(at)jonathangardner(dot)net
- Re: PostgreSQL as a local in-memory cache
- From: jgardner(at)jonathangardner(dot)net
- Re: PostgreSQL as a local in-memory cache
- From: Josh Berkus
- PostgreSQL as a local in-memory cache
- Prev by Date: Re: PostgreSQL as a local in-memory cache
- Next by Date: Re: PostgreSQL as a local in-memory cache
- Previous by thread: Re: PostgreSQL as a local in-memory cache
- Next by thread: Re: PostgreSQL as a local in-memory cache
- Indexes: