On Wed, Nov 01, 2000 at 10:16:58AM +0000, Poul L. Christiansen wrote:
> PostgreSQL hits the disk on UPDATE/DELETE/INSERT operations. SELECT's
> are cached, but the default cache is only ½MB of RAM. You can change
> this to whatever you want.
That sound like a very cool thing to do, and the default seems awfully
conservative, given the average server´s RAM equipment nowadays. If you
have a small Linux server with 128 MB of RAM, it would be interesting to
see what happens, performance-wise, if you increase the cache for
selects to, for instance, 64 MB. Has anyone tried to benchmark this? How
would you benchmark it? Where do you change this cache size? How do you
keep the cache from being swapped out to disk (which would presumably
all but eradicate the benefits of such a measure)?
Cheers Frank
--
frank joerdens
joerdens new media
urbanstr. 116
10967 berlin
germany
e: frank@joerdens.de
t: +49 (0)30 69597650
f: +49 (0)30 7864046
h: http://www.joerdens.de
pgp public key: http://www.joerdens.de/pgp/frank_joerdens.asc
