X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id EF7959DCB74 for ; Fri, 17 Mar 2006 10:57:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 90392-07 for ; Fri, 17 Mar 2006 10:57:43 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by postgresql.org (Postfix) with ESMTP id EEA1B9DCB61 for ; Fri, 17 Mar 2006 10:57:36 -0400 (AST) Received: by zproxy.gmail.com with SMTP id 8so546555nzo for ; Fri, 17 Mar 2006 06:57:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fzx6OyyioxjLpayZU4ZXOrs28BZ5KUAHcYb45IA8G16AFwATTZDoB+kWAwVFzlIkoilwyZFEswyIeO5ACa9fhYXaUA7eznqhTllkw2DQwFiTJ9xBrAhm/sHZQouPwUHLr6RXgP5iDhpvV18NSYdUIwB/O32DV+OOkJhjNtllOf4= Received: by 10.65.110.11 with SMTP id n11mr245981qbm; Fri, 17 Mar 2006 06:57:37 -0800 (PST) Received: by 10.65.135.10 with HTTP; Fri, 17 Mar 2006 06:57:36 -0800 (PST) Message-ID: Date: Fri, 17 Mar 2006 09:57:36 -0500 From: "Merlin Moncure" To: "Rodrigo Madera" Subject: Re: 1 TB of memory Cc: pgsql-performance@postgresql.org In-Reply-To: <3cf983d0603170625k370b4d29rcbdd5c7015fc18fa@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <8B16F5C8-DFC8-4694-902C-AE584E490530@pervasive.com> <3cf983d0603170625k370b4d29rcbdd5c7015fc18fa@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.137 required=5 tests=[AWL=0.137] X-Spam-Score: 0.137 X-Spam-Level: X-Archive-Number: 200603/275 X-Sequence-Number: 17712 On 3/17/06, Rodrigo Madera wrote: > I don't know about you databasers that crunch in some selects, updates > and deletes, but my personal developer workstation is planned to be a > 4x 300GB SATA300 with a dedicated RAID stripping controller (no > checksums, just speedup) and 4x AMD64 CPUs... not to mention 2GB for > each processor... all this in a nice server motherboard... no doubt, that will handle quite a lot of data. in fact, most databases (contrary to popular opinion) are cpu bound, not i/o bound.=20 However, at some point a different set of rules come into play. This point is constantly chaning due to the relentless march of hardware but I'd suggest that at around 1TB you can no longer count on things to run quickly just depending on o/s file caching to bail you out.=20 Or, you may have a single table + indexes thats 50 gb that takes 6 hours to vacuum sucking all your i/o. another useful aspect of SSD is the relative value of using system memory is much less, so you can reduce swappiness and tune postgres to rely more on the filesystem and give all your memory to work_mem and such. merlin