pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: amazon ec2
Date: Wed, 04 May 2011 17:02:53 -0700
Message-ID: <4DC1E92D.5020904@agliodbs.com> (raw)
In-Reply-To: <00C0C53C-7042-4C05-B6CD-68BFDF400C76@nasby.net>
References: <ADB48657-780F-4465-ABE6-752C2FB3AF48@gmail.com>
	<201105031241.20348.ahodgson@simkin.ca>
	<F3B854F7-53C8-4895-99BF-EB64BD6E5B53@gmail.com>
	<201105031309.52154.ahodgson@simkin.ca>
	<BANLkTinKbgzSGwg1GWTpwUCkwSpaCaebsA@mail.gmail.com>
	<4DC08420.7050602@2ndquadrant.com>
	<00C0C53C-7042-4C05-B6CD-68BFDF400C76@nasby.net>


> FWIW, EnterpriseDB's "InfiniCache" provides the same caching benefit. The way that works is when PG goes to evict a page from shared buffers that page gets compressed and stuffed into a memcache cluster. When PG determines that a given page isn't in shared buffers it will then check that memcache cluster before reading the page from disk. This allows you to cache amounts of data that far exceed the amount of memory you could put in a physical server.

So memcached basically replaces the filesystem?

That sounds cool, but I'm wondering if it's actually a performance
speedup.  Seems like it would only be a benefit for single-row lookups;
any large reads would be a mess.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



view thread (16+ messages)  latest in thread

Message-ID: <4DC1E92D.5020904@agliodbs.com>
Permalink:  ../4DC1E92D.5020904@agliodbs.com/
Also on:    postgresql.org/message-id/4DC1E92D.5020904@agliodbs.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com
  Subject: Re: amazon ec2
  In-Reply-To: <4DC1E92D.5020904@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox