Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 5B915633284 for ; Tue, 24 Mar 2009 20:16:34 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 49917-08 for ; Tue, 24 Mar 2009 20:16:27 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mail.postgresql.org (Postfix) with ESMTP id 0326E63310F for ; Tue, 24 Mar 2009 20:16:31 -0300 (ADT) Received: by yx-out-2324.google.com with SMTP id 8so1857568yxm.73 for ; Tue, 24 Mar 2009 16:16:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Fb7J9gDx3CZMp5xWuBU/5ta8CER2aH/IRhIjYiCXMKs=; b=ft5d+9K9TX1zDlfmYg0L9W9D1ElInO/itsS8f/0+3NsNWMAOAaBMfuZrkm1QPwX+l4 BAAKDtS6n7Y72rPAS2PtwrWkkzQ56R7DVjplLq31lDHeLHxkQr1w2cVtXS+9LBm+Dwtj 6dbNwh5ga8hTz/h6yv7jCK6k2DpHHVWycWAaw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=vzTrvA9QR67ZG4BidKwUQ4hZDj43BsuiR32IEXZzwggrTtamWGEUMEWxfcDS9tx/TQ QKsomdB3NIoOBW/H32zVmDSFokQuUsC/E9+OvBaN4tdfVFGFuuh81emoP50tQCS/OYjN 8MKu7r5WMPRZjq4TEbgF/xDtWd6DPlzWDb1TY= MIME-Version: 1.0 Received: by 10.100.107.3 with SMTP id f3mr8426878anc.92.1237936590588; Tue, 24 Mar 2009 16:16:30 -0700 (PDT) In-Reply-To: References: <8609D1C0-3ECD-4A4F-B9C6-1FC8496EDC7A@gmail.com> <87d4ch0z4z.fsf@oxford.xeocode.com> <9719B46B-6CF8-4710-BE2A-1DE8E1C0C05B@gmail.com> <468A01CE-F631-4B2F-8882-03C381503DA2@gmail.com> <1E10954A-136D-4E1E-B576-31D09EE46499@gmail.com> Date: Tue, 24 Mar 2009 17:16:30 -0600 Message-ID: Subject: Re: High CPU Utilization From: Scott Marlowe To: Ron Cc: Joe Uhl , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/352 X-Sequence-Number: 33274 On Tue, Mar 24, 2009 at 4:58 PM, Ron wrote: > At 02:47 PM 3/24/2009, Joe Uhl wrote: > >> Turns out we may have an opportunity to purchase a new database server >> with this increased load. =A0Seems that the best route, based on feedbac= k to >> this thread, is to go whitebox, get quad opterons, and get a very good d= isk >> controller. >> >> Can anyone recommend a whitebox vendor? > > I'll 2nd the Aberdeen recommendation. =A0I'll add Pogolinux to that list = as > well. > > >> Is there a current controller anyone on this list has experience with th= at >> they could recommend? > > The 2 best performing RAID controller vendors at this time are AMCC (AKA > 3Ware) and Areca. > In general, the 8+ port Areca's with their BB cache maxed outperform ever= y > other controller available. > > >> This will be a bigger purchase so will be doing research and benchmarkin= g >> but any general pointers to a vendor/controller greatly appreciated. > > Be =3Dvery=3D careful to thoroughly bench both the AMD and Intel CPU opti= ons. > =A0It is far from clear which is the better purchase. My anecdotal experience has been that the Opterons stay afloat longer as load increases, but I haven't had machines with similar enough hardware to really test that. > I'd be very interested to see the results of your research and benchmarks > posted here on pgsql-performance. Me too. I'm gonna spend some time this summer benchmarking and tuning the database servers that I pretty much had to burn in and put in production this year due to time pressures.