On 2011-03-18 01:51, Oliver Charles wrote:
Hello, At MusicBrainz we're looking to get a new database server, and are hoping to buy this in the next couple of days. I'm mostly a software guy, but I'm posting this on behalf of Rob, who's actually going to be buying the hardware. Here's a quote of what we're looking to get:
I think most of it has been said already: * Battery backed write cache * See if you can get enough memory to make all of your "active" dataset fit in memory. (typically not that hard in 2011). * Dependent on your workload of-course, you're typically not bottlenecked by the amount of cpu-cores, so strive for fewer faster cores. * As few sockets as you can screeze you memory and cpu-requirements onto. * If you can live with (or design around) the tradeoffs with SSD it will buy you way more performance than any significant number of rotating drives. (a good backup plan with full WAL-log to a second system as an example). -- Jesper -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
