From: Matt Clark <matt@ymogen.net>
To: Steve Atkins <steve@blighty.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Mon, 27 Sep 2004 22:41:52 +0100
Message-ID: <41588920.6020304@ymogen.net> (raw)
In-Reply-To: <20040927205345.GA29554@gp.word-to-the-wise.com>
References: <BAY18-DAV6m5UxP9Fek0002fd87@hotmail.com>
<00e801c4a4b6$5526dd30$8300a8c0@solent>
<330532b604092711591491303a@mail.gmail.com>
<415875C0.3010805@ymogen.net>
<20040927205345.GA29554@gp.word-to-the-wise.com>
>Any competently written application where caching results would be a
>suitable performance boost can already implement application or
>middleware caching fairly easily, and increase performance much more
>than putting result caching into the database would.
>
>
>
I guess the performance increase is that you can spend $10,000 on a
developer, or $10,000 on hardware, and for the most part get a more
reliable result the second way. MemcacheD is fine(ish), but it's not a
panacea, and it's more than easy to shoot yourself in the foot with it.
Caching is hard enough that lots of people do it badly - I'd rather use
an implementation from the PG team than almost anywhere else.
>I don't see caching results in the database as much of a win for most
>well written applications. Toy benchmarks, sure, but for real apps it
>seems it would add a lot of complexity, and violate the whole point of
>using an ACID database.
>
>
>
Well the point surely is to _remove_ complexity from the application,
which is written by God Knows Who, and put it in the DB, which is
written by God And You. And you can still have ACID (cached data is not
the same as stale data, although once you have the former, the latter
can begin to look tempting sometimes).
M
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: matt@ymogen.net, steve@blighty.com
Subject: Re: Caching of Queries
In-Reply-To: <41588920.6020304@ymogen.net>
* 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