From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Lars Heidieker <lars(at)heidieker(dot)de> |
Cc: | Walter Vaughan <wvaughan(at)steelerubber(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Hardware |
Date: | 2007-02-06 17:23:05 |
Message-ID: | 1170782584.5451.104.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2007-02-06 at 10:33, Lars Heidieker wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On 6 Feb 2007, at 15:59, Walter Vaughan wrote:
>
> > I need to purchase a new server to put posgresql on that will be
> > acting as the DBMS server for Apache ofBiz soon. While googling
> > around for performance tweaks I saw this at http://revsys.com/
> > writings/postgresql-performance.html
> >
> > <quote>
> > CPUs — The more CPUs the better, however if your database does not
> > use many complex functions your money is best spent on a better
> > disk subsystem. Also, avoid Intel Xeon processors with PostgreSQL
> > as there is a problem with the context switching in these
> > processors that gives sub-par performance. Opterons are generally
> > accepted as being a superior CPU for PostgreSQL databases.
> > </quote>
> >
> > Is this still true in regards to Xeon's? I was looking at a server
> > with Quad Core Xeon 2 5335 @ 2.0GHz.
> >
> > And at http://www.powerpostgresql.com/PerfList
> >
>
> It seems to be outdated. As far as I know it was supposed to warn for
> the HyperThreading things.
It wasn't just hyperthreading. The older xeons tended to have more CPU
horsepower than cache bandwidth, and this resulted in them going into
swap storms whether hyperthreading was on or not. It was just easier to
trigger with hyperthreading.
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Tassonis | 2007-02-06 17:25:14 | Cursor timeout in postgres |
Previous Message | Scott Marlowe | 2007-02-06 16:59:07 | Re: PostgreSQL/FireBird |