The suggestion that we are saturating the memory bus
makes a lot of sense. We originally started with a
low setting for shared buffers and resized it to fit
all our tables (since we have memory to burn). That
improved stand alone performance but not concurrent
performance - this would explain tha
Josh Berkus <[EMAIL PROTECTED]> writes:
>> We are running with shared buffers large enough to hold the
>> entire database
> Which is bad. This is not what shared buffers are for. See:
> http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
In fact, that may be the cause of the performan
Simon,
> The issue is that no matter how much query load we throw at our server it
> seems almost impossible to get it to utilize more than 50% cpu on a
> dual-cpu box. For a single connection we can use all of one CPU, but
> multiple connections fail to increase the overall utilization (although
