X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AFC29329EAB for ; Tue, 12 Oct 2004 02:48:49 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 39405-05 for ; Tue, 12 Oct 2004 01:48:37 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id D3905329E7E for ; Tue, 12 Oct 2004 02:48:40 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i9C1maJ7042300 for ; Tue, 12 Oct 2004 01:48:36 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i9C1ZD83039309 for pgsql-performance@postgresql.org; Tue, 12 Oct 2004 01:35:13 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: IBM P-series machines (was: Excessive context Date: Mon, 11 Oct 2004 21:34:44 -0400 Organization: cbbrowne Computing Inc Lines: 55 Message-ID: References: <4162CA14.6080206@lulu.com> <200410050947.36174.josh@agliodbs.com> <20041011173819.GB22076@phlogiston.dyndns.org> <1097518852.54644.20.camel@home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:RQnEtCKDkofbB7SGiselPsJNRl8= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/151 X-Sequence-Number: 8627 pg@rbt.ca (Rod Taylor) wrote: > On Mon, 2004-10-11 at 13:38, Andrew Sullivan wrote: >> On Tue, Oct 05, 2004 at 09:47:36AM -0700, Josh Berkus wrote: >> > As long as you're on x86, scaling outward is the way to go. If >> > you want to continue to scale upwards, ask Andrew Sullivan about >> > his experiences running PostgreSQL on big IBM boxes. But if you >> > consider an quad-Opteron server expensive, I don't think that's >> > an option for you. > >> The 650s are not cheap, but boy are they fast. I don't have any >> numbers I can share, but I can tell you that we recently had a few >> days in which our write load was as large as the entire write load >> for last year, and you couldn't tell. It is too early for us to >> say whether the P series lives up to its billing in terms of >> relibility: the real reason we use these machines is reliability, >> so if approaching 100% uptime isn't important to you, the speed may >> not be worth it. > > Agreed completely, and the 570 knocks the 650 out of the water -- > nearly double the performance for math heavy queries. Beware vendor > support for Linux on these things though -- we ran into many of the > same issues with vendor support on the IBM machines as we did with > the Opterons. The 650s are running AIX, not Linux. Based on the "Signal 11" issue, I'm not certain what would be the 'best' answer. It appears that the problem relates to proprietary bits of AIX libc. In theory, that would have been more easily resolvable with a source-available GLIBC. On the other hand, I'm not sure what happens to support for any of the interesting hardware extensions. I'm not sure, for instance, that we could run HACMP on Linux on this hardware. As for "vendor support" for Opteron, that sure looks like a trainwreck... If you're going through IBM, then they won't want to respond to any issues if you're not running a "bog-standard" RHAS/RHES release from Red Hat. And that, on Opteron, is preposterous, because there's plenty of the bits of Opteron support that only ever got put in Linux 2.6, whilst RHAT is still back in the 2.4 days. In a way, that's just as well, at this point. There's plenty of stuff surrounding this that is still pretty experimental; the longer RHAT waits to support 2.6, the greater the likelihood that Linux support for Opteron will have settled down to the point that the result will actually be supportable by RHAT, and by proxy, by IBM and others. There is some risk that if RHAT waits _too_ long for 2.6, people will have already jumped ship to SuSE. No benefits without risks... -- (reverse (concatenate 'string "gro.mca" "@" "enworbbc")) http://www.ntlug.org/~cbbrowne/rdbms.html If at first you don't succeed, then you didn't do it right! If at first you don't succeed, then skydiving definitely isn't for you.