From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | mario(dot)splivalo(at)mobart(dot)hr |
Cc: | "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: scaling up postgres |
Date: | 2006-06-11 23:21:54 |
Message-ID: | 448CA592.4040506@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Mario Splivalo wrote:
> On Sat, 2006-06-03 at 11:43 +0200, Steinar H. Gunderson wrote:
>> On Sat, Jun 03, 2006 at 10:31:03AM +0100, fzied(at)planet(dot)tn wrote:
>>> I do have 2 identical beasts (4G - biproc Xeon 3.2 - 2 Gig NIC)
>>> One beast will be apache, and the other will be postgres.
>>> I'm using httperf/autobench for measurments and the best result I can get
>>> is that my system can handle a trafiic of almost 1600 New con/sec.
>> What version of PostgreSQL? (8.1 is better than 8.0 is much better than 7.4.)
>> Have you remembered to turn HT off? Have you considered Opterons instead of
>> Xeons? (The Xeons generally scale bad with PostgreSQL.) What kind of queries
>
> Could you point out to some more detailed reading on why Xeons are
> poorer choice than Opterons when used with PostgreSQL?
It isn't just PostgreSQL. It is any database. Opterons can move memory
and whole lot faster then Xeons.
Joshua D. Drake
>
> Mario
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Qingqing Zhou | 2006-06-12 02:50:28 | Re: Variation between query runtimes |
Previous Message | Steinar H. Gunderson | 2006-06-11 21:43:41 | Re: scaling up postgres |