From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Michael Adler <adler@pobox.com>
Subject: Re: memcached and PostgreSQL
Date: Tue, 16 Nov 2004 21:47:54 -0800
Message-ID: <200411162147.54831.josh@agliodbs.com> (raw)
In-Reply-To: <20041117040024.GB8838@pobox.com>
References: <20041117040024.GB8838@pobox.com>
Michael,
> So What does memcached offer pgsql users? It would still seem to offer
> the benefit of a multi-machined cache.
Yes, and a very, very fast one too ... like, 120,000 operations per second.
PostgreSQL can't match that because of the overhead of authentication,
security, transaction visibility checking, etc.
So memcached becomes a very good place to stick data that's read often but not
updated often, or alternately data that changes often but is disposable. An
example of the former is a user+ACL list; and example of the latter is web
session information ... or simple materialized views.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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, adler@pobox.com
Subject: Re: memcached and PostgreSQL
In-Reply-To: <200411162147.54831.josh@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