pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Denis Lussier <denisl@enterprisedb.com>
To: Florian Weimer <fweimer@bfk.de>
Cc: Arjen van der Meijden <acmmailing@tweakers.net>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: Jonathan Ballet <jon@multani.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performances with new Intel Core* processors
Date: Thu, 3 Aug 2006 01:08:52 -0400
Message-ID: <5f820f750608022208ka5a2f81t4ac39d583685daf3@mail.gmail.com> (raw)
In-Reply-To: <8264hchq4a.fsf@mid.bfk.de>
References: <44CDFD44.8080307@multani.info>
	<b42b73150607310852o347833a1l5866681b9fbf0124@mail.gmail.com>
	<44CE3023.3020402@tweakers.net>
	<8264hchq4a.fsf@mid.bfk.de>

My theory, based entirely on what I have read in this thread, is that a low
end server (really a small workstation) with an Intel Dual Core CPU is
likely an excellent PG choice for the lowest end.

I'll try to snag an Intel Dual Core workstation in the near future and
report back DBT2 scores comparing it to a similarly equiped 1 socket AMD
dual core workstation.   I'll keep the data size small to fit entirely in
RAM so the DBT2 isn't it's usual disk bound dog when you run it the "right"
way (according to tpc-c guidelines).

--Denis
   Dweeb from EnterpriseDB

On 8/1/06, Florian Weimer <fweimer@bfk.de> wrote:
>
> * Arjen van der Meijden:
>
> > For a database system, however, processors hardly ever are the main
> > bottleneck, are they?
>
> Not directly, but the choice of processor influences which
> chipsets/mainboards are available, which in turn has some impact on
> the number of RAM slots.  (According to our hardware supplier, beyound
> 8 GB, the price per GB goes up sharply.)  Unfortunately, it seems that
> the Core 2 Duo mainboards do not change that much in this area.
>
> --
> Florian Weimer                <fweimer@bfk.de>
> BFK edv-consulting GmbH       http://www.bfk.de/
> Durlacher Allee 47            tel: +49-721-96201-1
> D-76131 Karlsruhe             fax: +49-721-96201-99
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
>

view thread (9+ messages)

Message-ID: <5f820f750608022208ka5a2f81t4ac39d583685daf3@mail.gmail.com>
Permalink:  ../5f820f750608022208ka5a2f81t4ac39d583685daf3@mail.gmail.com/
Also on:    postgresql.org/message-id/5f820f750608022208ka5a2f81t4ac39d583685daf3@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: denisl@enterprisedb.com, fweimer@bfk.de, acmmailing@tweakers.net, mmoncure@gmail.com, jon@multani.info
  Subject: Re: Performances with new Intel Core* processors
  In-Reply-To: <5f820f750608022208ka5a2f81t4ac39d583685daf3@mail.gmail.com>
  References: <44CDFD44.8080307@multani.info> <b42b73150607310852o347833a1l5866681b9fbf0124@mail.gmail.com> <44CE3023.3020402@tweakers.net> <8264hchq4a.fsf@mid.bfk.de> <5f820f750608022208ka5a2f81t4ac39d583685daf3@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox