From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
Cc: | PostgreSQL general list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Solaris and effective_cache_size |
Date: | 2002-02-15 16:17:42 |
Message-ID: | 14226.1013789862@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andrew Sullivan <andrew(at)libertyrms(dot)info> writes:
> Solaris is _much_ more aggressive about disk caching than Linux is,
> it seems. I suspected that adjusting the effective_cache_size
> setting might therefore help.
> Using pgbench, I discovered a performance advantage of almost 10% by
> increasing the setting from the default 1000 to 1500. I am not sure
> whether this figure will hold up, but it was consistent over multiple
> tests.
Actually, the default 1000 setting is probably very much on the low side
--- that's only equivalent to 8 meg of disk cache space after all, and
on any reasonably modern box there's probably lots more RAM than that
being used for disk cache.
However, I'm quite surprised to hear that tweaking effective_cache_size
affects pgbench results at all. I'd have thought that all the queries
used by pgbench would be indexscans anyway...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Yeoh | 2002-02-15 16:24:43 | Re: psql & HTML |
Previous Message | Peter Peltonen | 2002-02-15 16:11:08 | Redirecting query's output to a textfile? |