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 50BF15379D for ; Wed, 6 Apr 2005 14:26:35 +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 52456-06 for ; Wed, 6 Apr 2005 13:26:32 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id 9290753797 for ; Wed, 6 Apr 2005 14:26:30 +0100 (BST) Received: (qmail 23028 invoked from network); 6 Apr 2005 15:26:55 +0200 Received: from unknown (HELO localhost) (boutiquenumerique-lists@192.168.0.4) by boutiquenumerique.com with SMTP; 6 Apr 2005 15:26:55 +0200 Date: Wed, 06 Apr 2005 15:26:33 +0200 To: "Steinar H. Gunderson" , pgsql-performance@postgresql.org Subject: Re: Follow-Up: How to improve db performance with $7K? References: <4244A90B.2030200@sfnet.cc> <42453273.2060509@turtle-entertainment.de> <200503261255.59007.josh@agliodbs.com> <42455DEC.2080301@sfnet.cc> <1112049794.23284.29.camel@localhost.localdomain> <424840AE.3050200@sfnet.cc> <1112107974.7903.28.camel@sixtyfour.internetstaff.com> <424CAB5D.9020807@sfnet.cc> <20050406044456.GA19518@filer> <20050406112817.GB31767@uio.no> From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <42453273.2060509@turtle-entertainment.de> User-Agent: Opera M2(BETA2)/8.0 (Linux, build 987) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/95 X-Sequence-Number: 11492 > and we get about 65MB/sec sustained when writing to an ext3 filesystem > (actually, when wgetting a file off the gigabit LAN :-) ). I haven't Well, unless you have PCI 64 bits, the "standard" PCI does 133 MB/s which is then split exactly in two times 66.5 MB/s for 1) reading from the PCI network card and 2) writing to the PCI harddisk controller. No wonder you get this figure, you're able to saturate your PCI bus, but it does not tell you a thing on the performance of your disk or network card... Note that the server which serves the file is limited in the same way unless the file is in cache (RAM) or it's PCI64. So... > tested > reading, though. > > /* Steinar */