Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id C52FAB5DBDE for ; Wed, 25 May 2011 05:51:59 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 74695-01 for ; Wed, 25 May 2011 08:51:52 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f46.google.com (mail-bw0-f46.google.com [209.85.214.46]) by mail.postgresql.org (Postfix) with ESMTP id 92AB6B5DBDD for ; Wed, 25 May 2011 05:51:52 -0300 (ADT) Received: by bwz15 with SMTP id 15so6340420bwz.19 for ; Wed, 25 May 2011 01:51:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=j5r0Xl0c+4zBOmeRJoRdkwQtBcfshdrTEOllcEax1N8=; b=wxWMAquccD2A0u78TDhBWLcK88chpkMdhL9/SbqvwFMBVn1FVVJsIdKy+4LxDPj1V7 r/ouLB5uGcQdMMneUTnMKFnwuUFiLcUdjz6LBE4qNBlJvBKhDq9LrnvmwEX5t7b9nV1g XQE/V89qhbiz5/rUmrGoQcdP1RaaR1M236WiY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=dFmyrQ9SRavbNp2Su/S6nhjULSNi6p7kAjYlnJq+tJeufvTH8wXYwQLW8XMGs64n4n STXlrCV9oumPeRL5g7NvhedhKMZ67I2GM4NuKcNMrVQ+gKBeTgetHDKpwpeVgoNTD5C2 0fxxIP7rGmhIzXGiEQzz3pAeCpiKQHVPgV/wM= Received: by 10.204.48.140 with SMTP id r12mr3846940bkf.51.1306313511708; Wed, 25 May 2011 01:51:51 -0700 (PDT) Received: from [10.64.1.26] ([213.108.72.250]) by mx.google.com with ESMTPS id d25sm5067342bkd.5.2011.05.25.01.51.49 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2011 01:51:50 -0700 (PDT) Message-ID: <4DDCC32D.2000901@gmail.com> Date: Wed, 25 May 2011 11:51:57 +0300 From: Vitalii Tymchyshyn User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Greg Smith CC: pgsql-performance@postgresql.org Subject: Re: [PERFORMANCE] expanding to SAN: which portion best to move References: <4DC0D968.3030106@krogh.cc> <4DC0E525.4060108@krogh.cc> <4DD2441D.8040500@postnewspapers.com.au> <4DDBFD94.9010407@2ndQuadrant.com> In-Reply-To: <4DDBFD94.9010407@2ndQuadrant.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.345 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=1.553, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001 X-Spam-Level: X-Archive-Number: 201105/333 X-Sequence-Number: 43842 24.05.11 21:48, Greg Smith написав(ла): > > Bitmap heap scan: Here, the exact list of blocks to fetch is known in > advance, they're random, and it's quite possible for the kernel to > schedule them more efficiently than serial access of them can do. This > was added as the effective_io_concurrency feature (it's the only thing > that feature impacts), which so far is only proven to work on Linux. > Any OS implementing the POSIX API used will also get this however; > FreeBSD was the next likely candidate that might benefit when I last > looked around. FreeBSD unfortunately do not have the support :( It has AIO, but does not have the call needed to enable this settings. Best regards, Vitalii Tymchyshyn