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 968FB53527 for ; Tue, 29 Mar 2005 19:11:22 +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 37301-05 for ; Tue, 29 Mar 2005 18:11:12 +0000 (GMT) Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id B6BE553459 for ; Tue, 29 Mar 2005 19:11:11 +0100 (BST) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1DGLBA-0001sa-00; Tue, 29 Mar 2005 13:11:04 -0500 To: pg@fastcrypt.com Cc: pgsql-performance@postgresql.org Subject: Re: How to improve db performance with $7K? References: <42443863.4040302@sfnet.cc> <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> <42494741.7060806@fastcrypt.com> In-Reply-To: <42494741.7060806@fastcrypt.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 29 Mar 2005 13:11:04 -0500 Message-ID: <87ekdyz5jb.fsf@stark.xeocode.com> Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.01 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/641 X-Sequence-Number: 11346 Dave Cramer writes: > PFC wrote: > > > > My Laptop does 19 MB/s (reading <10 KB files, reiser4) ! > > Yeah, 35Mb per sec is slow for a raid controller, the 3ware mirrored is > about 50Mb/sec, and striped is about 100 Well you're comparing apples and oranges here. A modern 7200rpm drive should be capable of doing 40-50MB/s depending on the location of the data on the disk. But that's only doing sequential access of data using something like dd and without other processes intervening and causing seeks. In practice it seems a busy databases see random_page_costs of about 4 which for a drive with 10ms seek time translates to only about 3.2MB/s. I think the first order of business is getting pg_xlog onto its own device. That alone should remove a lot of the seeking. If it's an ext3 device I would also consider moving the journal to a dedicated drive as well. (or if they're scsi drives or you're sure the raid controller is safe from write caching then just switch file systems to something that doesn't journal data.) -- greg