X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id F31D19FB27B for ; Wed, 16 Aug 2006 03:17:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 11529-09 for ; Wed, 16 Aug 2006 03:17:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exprod6og52.obsmtp.com (exprod6og52.obsmtp.com [64.18.1.185]) by postgresql.org (Postfix) with SMTP id 2083B9FB1F8 for ; Wed, 16 Aug 2006 03:17:52 -0300 (ADT) Received: from source ([63.240.6.46]) by exprod6ob52.postini.com ([64.18.5.12]) with SMTP; Tue, 15 Aug 2006 23:17:43 PDT Received: from 172.16.1.25 by mail.mi8.com with ESMTP (- Welcome to Mi8 Corporation www.Mi8.com (D2)); Wed, 16 Aug 2006 02:17:36 -0400 X-Server-Uuid: 7829E76E-BB9E-4995-8473-3C0929DF7DD1 Received: from MI8NYCMAIL06.Mi8.com ([172.16.1.160]) by D01HOST03.Mi8.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 Aug 2006 02:17:36 -0400 Received: from 69.181.100.71 ([69.181.100.71]) by MI8NYCMAIL06.Mi8.com ( [172.16.1.219]) via Exchange Front-End Server mi8owa.mi8.com ( [172.16.1.106]) with Microsoft Exchange Server HTTP-DAV ; Wed, 16 Aug 2006 06:17:35 +0000 User-Agent: Microsoft-Entourage/11.2.5.060620 Date: Tue, 15 Aug 2006 23:17:32 -0700 Subject: Re: Dell PowerEdge 2950 performance From: "Luke Lonergan" To: "Bucky Jordan" , "Vivek Khera" , "Pgsql-Performance ((E-mail))" Message-ID: Thread-Topic: [PERFORM] Dell PowerEdge 2950 performance Thread-Index: AcbAn4h2d1PVc/GzRBy+xnSYs+pzfgACNZ0QABTSWog= In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4104A01@MAIL.corp.lumeta.com> MIME-Version: 1.0 X-OriginalArrivalTime: 16 Aug 2006 06:17:36.0623 (UTC) FILETIME=[AB14CFF0:01C6C0FB] X-WSS-ID: 68FC670A2NG1826753-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.657 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, RCVD_NUMERIC_HELO X-Spam-Level: * X-Archive-Number: 200608/260 X-Sequence-Number: 20445 Cool - seems like the posters caught that "auto memory pick" problem before you posted, but you got the 16GB/8k parts right. Now we're looking at realistic numbers - 790 seeks/second, 244MB/s sequential write, but only 144MB/s sequential reads, perhaps 60% of what it should be. Seems like a pretty good performer in general - if it was Linux I'd play with the max readahead in the I/O scheduler to improve the sequential reads. - Luke On 8/15/06 1:21 PM, "Bucky Jordan" wrote: > Luke, > > For some reason it looks like bonnie is picking a 300M file. > >> bonnie++ -d bonnie > Version 1.03 ------Sequential Output------ --Sequential Input- > --Random- > -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- > --Seeks-- > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP > /sec %CP > 300M 179028 99 265358 41 270175 57 167989 99 +++++ +++ > +++++ +++ > ------Sequential Create------ --------Random > Create-------- > -Create-- --Read--- -Delete-- -Create-- --Read--- > -Delete-- > files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP > /sec %CP > 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ > +++++ +++ > ,300M,179028,99,265358,41,270175,57,167989,99,+++++,+++,+++++,+++,16,+++ > ++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++ > > So here's results when I force it to use a 16GB file, which is twice the > amount of physical ram in the system: > >> bonnie++ -d bonnie -s 16000:8k > Version 1.03 ------Sequential Output------ --Sequential Input- > --Random- > -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- > --Seeks-- > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP > /sec %CP > 16000M 158539 99 244430 50 58647 29 83252 61 144240 21 > 789.8 7 > ------Sequential Create------ --------Random > Create-------- > -Create-- --Read--- -Delete-- -Create-- --Read--- > -Delete-- > files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP > /sec %CP > 16 7203 54 +++++ +++ +++++ +++ 24555 42 +++++ +++ > +++++ +++ > ,16000M,158539,99,244430,50,58647,29,83252,61,144240,21,789.8,7,16,7203, > 54,+++++,+++,+++++,+++,24555,42,+++++,+++,+++++,+++ > > ... from Vivek... > which is an issue with freebsd and bonnie++ since it doesn't know > that freebsd can use large files natively (ie, no large file hacks > necessary). the freebsd port of bonnie takes care of this, if you > use that instead of compiling your own. > ... > > Unfortunately I had to download and build by hand, since only bonnie++ > 1.9x is available in BSD 6.1 ports when I checked. > > One other question- would the following also be mostly a test of RAM? I > wouldn't think so since it should force it to sync to disk... > time bash -c "(dd if=/dev/zero of=/data/bigfile count=125000 bs=8k && > sync)" > > Oh, and while I'm thinking about it, I believe Postgres uses 8k data > pages correct? On the RAID, I'm using 128k stripes. I know there's been > posts on this before, but is there any way to tell postgres to use this > in an effective way? > > Thanks, > > Bucky > > -----Original Message----- > From: pgsql-performance-owner@postgresql.org > [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Vivek Khera > Sent: Tuesday, August 15, 2006 3:18 PM > To: Pgsql-Performance ((E-mail)) > Subject: Re: [PERFORM] Dell PowerEdge 2950 performance > > > On Aug 15, 2006, at 2:50 PM, Luke Lonergan wrote: > >> I don't know why I missed this the first time - you need to let >> bonnie++ >> pick the file size - it needs to be 2x memory or the results you >> get will >> not be accurate. > > which is an issue with freebsd and bonnie++ since it doesn't know > that freebsd can use large files natively (ie, no large file hacks > necessary). the freebsd port of bonnie takes care of this, if you > use that instead of compiling your own. > >