Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id BECAF65017A for ; Mon, 17 Nov 2008 13:31:08 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 06287-01 for ; Mon, 17 Nov 2008 13:31:04 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ulysses.lattica.com (lattica.com [204.14.19.114]) by mail.postgresql.org (Postfix) with ESMTP id 51AF964FE47 for ; Mon, 17 Nov 2008 13:31:04 -0400 (AST) Received: from localhost (ulysses.lattica.com [127.0.0.1]) by ulysses.lattica.com (Postfix) with ESMTP id 2FE0C7383DD; Mon, 17 Nov 2008 12:31:03 -0500 (EST) X-Virus-Scanned: amavisd-new at lattica.com Received: from ulysses.lattica.com ([127.0.0.1]) by localhost (ulysses.lattica.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t93NzdDrQ46B; Mon, 17 Nov 2008 12:31:02 -0500 (EST) Received: from [192.168.3.11] (CPE00010242152b-CM0011aec8bfb4.cpe.net.cable.rogers.com [99.253.168.241]) by ulysses.lattica.com (Postfix) with ESMTP id 7F7AA7380A7; Mon, 17 Nov 2008 12:31:02 -0500 (EST) Subject: Re: Bad performance on simple query From: Dimi Paun To: Scott Marlowe Cc: pgsql-performance In-Reply-To: References: <1226937197.5760.89.camel@dimi.lattica.com> <1226941621.5760.97.camel@dimi.lattica.com> Content-Type: text/plain Organization: Lattica, Inc. Date: Mon, 17 Nov 2008 12:31:02 -0500 Message-Id: <1226943062.5760.103.camel@dimi.lattica.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/150 X-Sequence-Number: 31881 On Mon, 2008-11-17 at 10:16 -0700, Scott Marlowe wrote: > Ahhh. Keep in mind that if you just run the query, pgadminIII will > tell you how long it took to run AND return all the data across the > network, so it will definitely take longer then. But most of that's > network io wait so it's not a real issue unless you're saturating your > network. But that is brutal -- there's no way it can take 20ms for a request across an unloaded network. Moreover, I got something like this: pgadminIII | pgsql w/o index: 45ms 0.620ms w/ index 20ms 0.091ms How now I try to replicate, and I get 45ms in both cases. This is very misleading... -- Dimi Paun Lattica, Inc.