X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9CA38D1B8A4 for ; Thu, 28 Aug 2003 17:43:12 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 60654-01 for ; Thu, 28 Aug 2003 14:42:41 -0300 (ADT) Received: from ram.rentec.com (ram.rentec.com [192.5.35.66]) by svr1.postgresql.org (Postfix) with ESMTP id 7C92ED1B8BC for ; Thu, 28 Aug 2003 14:42:36 -0300 (ADT) Received: from rentec.com (IDENT:618@murre.rentec.com [192.5.35.148]) by ram.rentec.com (8.12.1/8.12.1) with ESMTP id h7SHgZw5011314; Thu, 28 Aug 2003 13:42:35 -0400 (EDT) Message-ID: <3F4E3F0B.9000802@rentec.com> Date: Thu, 28 Aug 2003 13:42:35 -0400 From: Michael Guerin User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20030703 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan Szabo Cc: pgsql-performance@postgresql.org Subject: Re: Simple queries take forever to run References: <20030828081914.A6403-100000@megazone.bigpanda.com> In-Reply-To: <20030828081914.A6403-100000@megazone.bigpanda.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/426 X-Sequence-Number: 3242 Stephan Szabo wrote: >On Thu, 28 Aug 2003, Michael Guerin wrote: > > > >>Stephan Szabo wrote: >> >> >> >>>On Wed, 27 Aug 2003, Michael Guerin wrote: >>> >>> >>> >>> >>> >>>>I'm running into some performance problems trying to execute simple >>>>queries. >>>> >>>>postgresql version 7.3.3 >>>>.conf params changed from defaults. >>>>shared_buffers = 64000 >>>>sort_mem = 64000 >>>>fsync = false >>>>effective_cache_size = 400000 >>>> >>>>ex. query: select * from x where id in (select id from y); >>>> >>>>There's an index on each table for id. SQL Server takes <1s to return, >>>>postgresql doesn't return at all, neither does explain analyze. >>>> >>>> >>>> >>>> >>>IN(subquery) is known to run poorly in 7.3.x and earlier. 7.4 is >>>generally much better (for reasonably sized subqueries) but in earlier >>>versions you'll probably want to convert into an EXISTS or join form. >>> >>> >>> >>> >>> >>> >>Something else seems to be going on, even switching to an exists clause >>gives much better but poor performance. >>count(*) where exists clause: Postgresql 19s, SQL Server <1s >>count(*) where not exists: 23.3s SQL Server 1.5s >> >> > >What does explain analyze show for the two queries? > > > > explain analyze select count(*) from tbltimeseries where exists(select uniqid from tblobjectname where timeseriesid = uniqid); Aggregate (cost=5681552.18..5681552.18 rows=1 width=0) (actual time=22756.64..22756.64 rows=1 loops=1) -> Seq Scan on tbltimeseries (cost=0.00..5680051.34 rows=600336 width=0) (actual time=22.06..21686.78 rows=1200113 loops=1) Filter: (NOT (subplan)) SubPlan -> Index Scan using idx_objectname on tblobjectname (cost=0.00..4.70 rows=1 width=4) (actual time=0.01..0.01 rows=0 loops=1200673) Index Cond: ($0 = uniqid) Total runtime: 22756.83 msec (7 rows) fiasco=# explain analyze select count(*) from tbltimeseries where exists(select uniqid from tblobjectname where timeseriesid = uniqid); QUERY PLAN ------------------------------------------------------------------------------------------------------------------------------------------------ explain analyze select count(*) from tbltimeseries where exists(select uniqid from tblobjectname where timeseriesid = uniqid); Aggregate (cost=5681552.18..5681552.18 rows=1 width=0) (actual time=19558.77..19558.77 rows=1 loops=1) -> Seq Scan on tbltimeseries (cost=0.00..5680051.34 rows=600336 width=0) (actual time=0.21..19557.73 rows=560 loops=1) Filter: (subplan) SubPlan -> Index Scan using idx_objectname on tblobjectname (cost=0.00..4.70 rows=1 width=4) (actual time=0.01..0.01 rows=0 loops=1200673) Index Cond: ($0 = uniqid) Total runtime: 19559.04 msec (7 rows)