Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 44A6C633704 for ; Sun, 4 Apr 2010 17:52:47 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 42141-01 for ; Sun, 4 Apr 2010 20:52:36 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mail.postgresql.org (Postfix) with ESMTP id 9D051632952 for ; Sun, 4 Apr 2010 17:52:36 -0300 (ADT) Received: by fxm22 with SMTP id 22so2739344fxm.34 for ; Sun, 04 Apr 2010 13:52:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=Eb3NHGB5JKZN+i3Nvdj4xfy4JKo7tO8LvqF3y7i3X5M=; b=dz307agmhp+JC3EnqoFyO+MMEqO5Rydi3HhZtYllzd0DHnR/D2vvnYYHH4IHKOEsYw CeWPzir7H2iKZAji/bYp8cxRHLtOWtzcPpPlWBRW/Dp1s9ufQeBE05Ja1gi1p0Llkrft OtAY98CFqqIxK4X3bfzVfmBAGroxjtQ9e3Tmc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tQ+yTUxV3wToN8py0blTe9TdVofcSQ1226B/CIpakxyI3gR0joPXGS/ieXPs4utYVR gDv7FX/O8RcArFN9+O5ENDwgcvStgx6SV2mlc3qf5q5jaPY5vuM1D5Opx4/PQcihcuy6 g1DVEOwq6e3Jbk1fxs9KpvGmTlj2mPBnPbpx8= MIME-Version: 1.0 Received: by 10.239.161.83 with HTTP; Sun, 4 Apr 2010 13:52:34 -0700 (PDT) In-Reply-To: References: Date: Sun, 4 Apr 2010 16:52:34 -0400 Received: by 10.239.131.199 with SMTP id 7mr414138hbo.175.1270414354922; Sun, 04 Apr 2010 13:52:34 -0700 (PDT) Message-ID: Subject: Re: Using high speed swap to improve performance? From: Robert Haas To: Christiaan Willemsen Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.185 tagged_above=-10 required=5 tests=BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 201004/31 X-Sequence-Number: 38281 On Fri, Apr 2, 2010 at 3:15 PM, Christiaan Willemsen wrote: > About a year ago we setup a machine with sixteen 15k disk spindles on > Solaris using ZFS. Now that Oracle has taken Sun, and is closing up Solaris, > we want to move away (we are more familiar with Linux anyway). > > So the plan is to move to Linux and put the data on a SAN using iSCSI (two > or four network interfaces). This however leaves us with with 16 very nice > disks dooing nothing. Sound like a wast of time. If we were to use Solaris, > ZFS would have a solution: use it as L2ARC. But there is no Linux filesystem > with those features (ZFS on fuse it not really an option). > > So I was thinking: Why not make a big fat array using 14 disks (raid 1, 10 > or 5), and make this a big and fast swap disk. Latency will be lower than > the SAN can provide, and throughput will also be better, and it will relief > the SAN from a lot of read iops. > > So I could create a 1TB swap disk, and put it onto the OS next to the 64GB > of memory. Then I can set Postgres to use more than the RAM size so it will > start swapping. It would appear to postgres that the complete database will > fit into memory. The question is: will this do any good? And if so: what > will happen? I suspect it will result in lousy performance because neither PG nor the OS will understand that some of that "memory" is actually disk. But if you end up testing it post the results back here for posterity... ...Robert