From: | Zydoon <fzied(at)planet(dot)tn> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: scaling up postgres |
Date: | 2006-06-13 21:24:44 |
Message-ID: | 448F2D1C.7090301@planet.tn |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gavin Hamill wrote:
> On Tue, 13 Jun 2006 14:28:49 -0500
> Scott Marlowe <smarlowe(at)g2switchworks(dot)com> wrote:
>
>> Search the performance archives for the last 4 or 5 months for PPC /
>> pseries machines.
>>
>> You'll find a very long thread about the disappointing performance the
>> tester got with a rather expensive P Series machine. And his happy
>> ending of testing on an Opteron machine.
>
> Amen, brother :)
>
> We hoped throwing a silly pSeries 650 would solve all our problems. Boy
> were we wrong... a world of pain...
>
> Don't go there - just buy an Opteron system - if you're talking about
> IBM big iron, a decent Opteron will cost you about as much as a couple
> of compilers and an on-site visit from IBM...
>
> Cheers,
> Gavin.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
Things cannot be clearer :)
I really know that opterons are the best I can have.
But for now I have to publish the results Sunday 25th on either the
xeons or the PPCs.
Tomorrow I'll conduct a deeper test, and come back.
Cheers.
- --
Zied Fakhfakh
GPG Key : gpg --keyserver subkeys.pgp.net --recv-keys F06B55B5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEjy0cS1DO7ovpKz8RAklqAKDC75a8SQUoGwNHGxu4ysZhNt5eJwCgt0mP
YHfZbYVS44kxFyxxEzs9KE0=
=aLbn
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Shaun Thomas | 2006-06-13 21:35:41 | Re: Confirmation of bad query plan generated by 7.4 |
Previous Message | Jim C. Nasby | 2006-06-13 21:21:24 | Re: scaling up postgres |