From: | Jesper Krogh <jesper(at)krogh(dot)cc> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Request for feedback on hardware for a new database server |
Date: | 2011-03-18 06:19:04 |
Message-ID: | 4D82F958.3080805@krogh.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-03-18 07:02:05 | Re: Disabling nested loops - worst case performance |
Previous Message | Adarsh Sharma | 2011-03-18 04:17:38 | Re: Help with Query Tuning |