Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2A51E650250 for ; Mon, 7 Jul 2008 12:09:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 75178-01 for ; Mon, 7 Jul 2008 12:09:28 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by postgresql.org (Postfix) with ESMTP id 104CB6507C1 for ; Mon, 7 Jul 2008 12:09:22 -0300 (ADT) Received: by el-out-1112.google.com with SMTP id o28so161018ele.10 for ; Mon, 07 Jul 2008 08:09:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=aYFUYGpLQVo3Qw9qGmLJIDEfQFy+33qq2XscIlbI5NQ=; b=rQ58G9kVpb9jFqMy66oguUqSPCuZ3AnABY34GQ140VyYwMXK35qJE/DbjfgHmoppLm a1bt/PBFGR8vcJL7ZitcffQeSbv7YMo9WrcdXbRIQx/ofbMxawzBb1Rwudh/U7jtoDjx RoO7jilqVhn3hqotN+6bK+1ZEriA38dIOue5M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=W5SBHlepm7/qBJn11aYARNXvY4Pe38wuFGo698VT4+p3q0I73NQ59Q1IwkHB5bkltQ T2dnbIJbrbJh3kXXQvf1bixB54Qxh+JahKGYBP3BYXfAw0yljEo7CKzfvsAzMKkBE8Hv 4TEEsLyvYZYRDHxsVGxN2H4kx+nHHM1igZ22o= Received: by 10.150.150.3 with SMTP id x3mr8388067ybd.53.1215443362099; Mon, 07 Jul 2008 08:09:22 -0700 (PDT) Received: by 10.150.186.15 with HTTP; Mon, 7 Jul 2008 08:09:22 -0700 (PDT) Message-ID: <36e682920807070809lbce9225wd1c67978d063dd01@mail.gmail.com> Date: Mon, 7 Jul 2008 11:09:22 -0400 From: "Jonah H. Harris" To: "Merlin Moncure" Subject: Re: Fusion-io ioDrive Cc: "Jeffrey Baker" , "pgsql-performance@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <36e682920807020441h11abd344j9c510722189cb3a2@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/61 X-Sequence-Number: 30661 On Mon, Jul 7, 2008 at 9:23 AM, Merlin Moncure wrote: > I have a lot of problems with your statements. First of all, we are > not really talking about 'RAM' storage...I think your comments would > be more on point if we were talking about mounting database storage > directly from the server memory for example. Sever memory and cpu are > involved to the extent that the o/s using them for caching and > filesystem things and inside the device driver. I'm not sure how those cards work, but my guess is that the CPU will go 100% busy (with a near-zero I/O wait) on any sizable workload. In this case, the current pgbench configuration being used is quite small and probably won't resemble this. > Also, your comments seem to indicate that having a slower device leads > to higher concurrency because it allows the process to yield and do > other things. This is IMO simply false. Argue all you want, but this is a fairly well known (20+ year-old) behavior. > With faster storage cpu loads will increase but only because the overall > system throughput increases and cpu/memory 'work' increases in terms > of overall system activity. Again, I said that response times (throughput) would improve. I'd like to see your argument for explaining how you can handle more CPU-only operations when 0% of the CPU is free for use. > Presumably as storage approaches speedsof main system memory > the algorithms of dealing with it will become simpler (not having to > go through acrobatics to try and making everything sequential) > and thus faster. We'll have to see. > I also find the remarks of software 'optimizing' for strict hardware > assumptions (L1+L2) cache a little suspicious. In some old programs I > remember keeping a giant C 'union' of critical structures that was > exactly 8k to fit in the 486 cpu cache. In modern terms I think that > type of programming (sans some specialized environments) is usually > counter-productive...I think PostgreSQL's approach of deferring as > much work as possible to the o/s is a great approach. All of the major database vendors still see an immense value in optimizing their algorithms and memory structures for specific platforms and CPU caches. Hence, if they're *paying* money for very-specialized industry professionals to optimize in this way, I would hesitate to say there isn't any value in it. As a fact, Postgres doesn't have those low-level resources, so for the most part, I have to agree that they have to rely on the OS. -Jonah