Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 09CDF63F838 for ; Thu, 14 Jan 2010 17:24:22 -0400 (AST) 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 78192-02-5 for ; Thu, 14 Jan 2010 21:24:07 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mail.postgresql.org (Postfix) with ESMTP id 21F0863652F for ; Thu, 14 Jan 2010 17:22:10 -0400 (AST) Received: by fxm27 with SMTP id 27so1340694fxm.3 for ; Thu, 14 Jan 2010 13:22:09 -0800 (PST) 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=/1ciytZu2pvWSjZTfAGQ7H/rJ9LkjLBbnvBgj22tH/w=; b=pRqdQ5BO1keVi0Uk+jEExWiOJEW2Eo6W/nqsA+K6XVhQ0vtUY4CE11wkrS+MXVvwPu rGcnMBLc6W3jhhoo1pIIgpwNj+Fte5fTSEKk73KX7yKq+TkW53ZjCCB9lIKgs+SXkBZf DzJxywmEuTtTxkerJzgmMv5Py0tbODoQ1UykQ= 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=o8hsJPg6x+Ii1MILGtjKOveajCRCd8XRVGhKxHLz0f4um2nlHIEtyYgqyLnVAF5dzf b8y4uvN8oEGEjwSvpeDZgSUjKwzIk5fqXpcMMByQ21o0hXEtC7AwL20Xta0D0ajq/AY+ yvNzWV8NCh6PjzCBuMe3+Y79wVnLOpcncDRwM= MIME-Version: 1.0 Received: by 10.216.90.209 with SMTP id e59mr520594wef.193.1263504129122; Thu, 14 Jan 2010 13:22:09 -0800 (PST) In-Reply-To: <3CD96C0AB4114484BFE358A3EDE61C01@iptel.com.ar> References: <3CD96C0AB4114484BFE358A3EDE61C01@iptel.com.ar> Date: Thu, 14 Jan 2010 14:22:09 -0700 Message-ID: Subject: Re: new server I/O setup From: Scott Marlowe To: Fernando Hevia Cc: 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=-2.48 tagged_above=-10 required=5 tests=AWL=0.119, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201001/310 X-Sequence-Number: 37190 On Thu, Jan 14, 2010 at 1:03 PM, Fernando Hevia wrot= e: > Hi all, > > I've just received=A0this new server: > 1 x XEON 5520 Quad Core w/ HT > 8 GB RAM 1066 MHz > 16 x SATA II Seagate Barracuda 7200.12 > 3ware 9650SE w/ 256MB BBU > > It will=A0run an Ubuntu=A08.04 LTS=A0Postgres 8.4 dedicated server. Its= =A0database > will be=A0getting between 100 and 1000 inserts per second (those are call > detail records of ~300 bytes each) of around 20 clients (voip gateways). > Other activity is mostly read-only and some non time-critical writes > generally=A0at off peak hours. > > So my first=A0choice was: > > 2=A0discs in RAID 1 for OS + pg_xlog partitioned with ext2. > 12 discs in RAID 10 for postgres data, sole partition with ext3. > 2 spares > > > My second choice is: > > 4 discs in RAID 10 for OS + pg_xlog partitioned with ext2 > 10 discs in RAID 10 for postgres, ext3 > 2 spares. > > The bbu cach=E9 will be enabled for both raid volumes. > > I justified my first choice in that WAL writes are=A0sequentially and OS > pretty much are too, so a RAID 1 probably would hold=A0ground against a 1= 2 > disc RAID 10 with random writes. I think your first choice is right. I use the same basic setup with 147G 15k5 SAS seagate drives and the pg_xlog / OS partition is almost never close to the same level of utilization, according to iostat, as the main 12 disk RAID-10 array is. We may have to buy a 16 disk array to keep up with load, and it would be all main data storage, and our pg_xlog main drive pair would be just fine. > I don't know in advance if I will manage to gather enough time to try out > both setups=A0so I wanted to know what you guys think of these 2 > alternatives.=A0Do you think a single RAID 1 will become=A0a bottleneck? = Feel > free to suggest a better setup I hadn't considered, it would be most > welcome. For 12 disks, most likely not. Especially since your load is mostly small randomish writes, not a bunch of big multi-megabyte records or anything, so the random access performance on the 12 disk RAID-10 should be your limiting factor. > Pd: any=A0clue if hdparm=A0works to deactive the disks write cache even i= f they > are behind the 3ware controller? Not sure, but I'm pretty sure the 3ware card already does the right thing and turns off the write caching.