Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 186552E0039 for ; Mon, 7 Apr 2008 17:20:21 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 92598-05 for ; Mon, 7 Apr 2008 17:20:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by developer.postgresql.org (Postfix) with ESMTP id B4D1B2E002C for ; Mon, 7 Apr 2008 17:20:17 -0300 (ADT) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (vanquish.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.162]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Mon, 07 Apr 2008 16:20:51 -0400 id 0005646E.47FA8223.0000E0FD Date: Mon, 7 Apr 2008 16:20:08 -0400 From: Bill Moran To: "Hell, Robert" Cc: pgsql-performance@postgresql.org Subject: Re: Looking for bottleneck during load test Message-Id: <20080407162008.c70fbb38.wmoran@collaborativefusion.com> In-Reply-To: References: Organization: Collaborative Fusion X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.8; i386-portbld-freebsd6.3) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/74 X-Sequence-Number: 29567 In response to "Hell, Robert" : > I tried different other tools for random IO (including a self written one= which does random lseek and read). >=20 > This tool, started during one of our tests, achieves 2 iops (8k each). > Started alone I get something about 1,500 iops with an avg latency of 100= ms. >=20 > We are using SAN (EMC CLARiiON CX 300) - are those ~7 MB/s really our bot= tleneck? > Any other tuning ideas? You know, with all the performance problems people have been bringing up with regard to SANs, I'm putting SAN in the same category as RAID-5 ... > -----Original Message----- > From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-ow= ner@postgresql.org] On Behalf Of Ivan Voras > Sent: Montag, 07. April 2008 14:38 > To: pgsql-performance@postgresql.org > Subject: Re: [PERFORM] Looking for bottleneck during load test >=20 > Hell, Robert wrote: > > We have a PostgreSQL 8.2.7 database (~230 GB) running on a machine with= 8 Intel Xeon Cores and 32 GB RAM (64-bit Linux 2.6.18). Data is stored on = an EMC=B2 CLARiiON on RAID 1/0 (8 x 146 GB 15k rpm).=20 > > When we do random I/O with a small test tool (reading random 8k blocks = from big files in 200 threads) on the disk we retrieve data with about 25 M= B/s. >=20 > How do you test random IO? Do you use this utility: > http://arctic.org/~dean/randomio/ ? >=20 > If not, try using it, with same parameters. It might be that the latency > is destroying your performance. Do you use NFS or are you accessing the > storage as SAN? >=20 >=20 > --=20 > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance >=20 > --=20 > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance --=20 Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran@collaborativefusion.com Phone: 412-422-3463x4023 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ****************************************************************