Re: XEON familiy 5000, 5100 or 5300?

From: "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Re: XEON familiy 5000, 5100 or 5300?
Date: 2007-01-15 07:08:28
Message-ID: 6C0CF58A187DA5479245E0830AF84F421D16BB@poweredge.attiksystem.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Shane wrote:

> No - a *core* is another cpu, basically you will have 2 or 4 cpu's in
> the one physical package.
>
> HT creates 2 virtual cpu's sharing the same cpu resources but the
> cores are seperate cpu's in themselves.
>
> The Quad-core will only benefit you more if you have more users
> running queries at the same time. Each core can run a query at the
> same time without slowing the others down (allowing for disk
> access/FSB limits).

Jose wrote:

> PostgreSQL handles each connection in a dedicated process, so you
> won't get better performance for a single connection by adding more
> CPUs (I mean, beyond the benefit of having the postmaster and the
> specific connection running in separate CPUs). This means that a
> query will not be resolved by more than one CPU. What you will get is
> better performance for multiple connections.

Shane, Jose,

Thanks for your answers. In my "very-low-concurrency scenario", I guess
then that multiple cores won't really help, as I suspected.

I think I have better take (for the same price) a ...

Dual-Core Intel Xeon 5060, 3.2 GHz, 4MB

... instead of a ...

Quad-Core Intel Xeon 5310, 1.6 GHz, 4MB

With my CPU-bound query, it will perform better.

But what about Hyperthreading then? Is it able to spread two threads
over two different cores? I guess the answer is no...

Philippe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Shoaib Mir 2007-01-15 09:40:12 Re: Backup the part of postgres database
Previous Message Joshua D. Drake 2007-01-15 05:42:09 Re: Backup the part of postgres database