If postgres is memory bandwidth constrained, what can be done to reduce its bandwidth use? Huge Pages could help some, by reducing page table lookups and making overall access more efficient. Compressed pages (speedy / lzo) in memory can help trade CPU cycles for memory usage for certain memory segments/pages -- this could potentially save a lot of I/O too if more pages fit in RAM as a result, and also make caches more effective. As I've noted before, the optimizer inappropriately choses the larger side of a join to hash instead of the smaller one in many cases on hash joins, which is less cache efficient. Dual-pivot quicksort is more cache firendly than Postgres' single pivit one and uses less memory bandwidth on average (fewer swaps, but the same number of compares). On 4/13/11 2:48 AM, "Glyn Astill" <glynastill@xxxxxxxxxxx> wrote: >--- On Tue, 12/4/11, Greg Smith <greg@xxxxxxxxxxxxxxx> wrote: > >> >> > >Thanks Greg. I've been through that post, but unfortunately there's no >settings that make a difference. > >However upon further investigation and looking at the manual for the R910 >here > >http://support.dell.com/support/edocs/systems/per910/en/HOM/HTML/install.h >tm#wp1266264 > >I've discovered we only have 4 of the 8 memory risers, and the manual >states that in this configuration we are running in "Power Optimized" >mode, rather than "Performance Optimized". > >We've got two of these machines, so I've just pulled all the risers from >one system, removed half the memory as indicated by that document from >Dell above, and now I'm seeing almost double the throughput. > > > >-- >Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) >To make changes to your subscription: >http://www.postgresql.org/mailpref/pgsql-performance -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
