From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Finding bottleneck |
Date: | 2005-08-19 13:37:19 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DD150@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> Kari Lavikka <tuner(at)bdb(dot)fi> writes:
> > However, those configuration changes didn't have significant effect
to
> > oprofile results. AtEOXact_CatCache consumes even more cycles.
>
> I believe I've fixed that for 8.1.
Relative to 8.0, I am seeing a dramatic, almost miraculous reduction in
CPU load times in 8.1devel. This is for ISAM style access patterns over
the parse/bind interface. (IOW one record at a time, 90% read, 10%
write).
Relative to commercial dedicated ISAM storage engines, pg holds up very
well except in cpu load, but 8.1 is a huge step towards addressing that.
So far, except for one minor (and completely understandable) issue with
bitmap issues, 8.1 has been a stellar performer. Also great is the
expansion of pg_locks view (which I didn't see mentioned in Bruce's TODO
list, just FYI).
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-08-19 13:58:22 | Re: sustained update load of 1-2k/sec |
Previous Message | Tom Lane | 2005-08-19 13:35:53 | Re: sustained update load of 1-2k/sec |