X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4BA2F8B9F8B for ; Thu, 10 Feb 2005 00:55:22 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56531-10 for ; Thu, 10 Feb 2005 00:55:05 +0000 (GMT) Received: from morework.geizhals.at (home.geizhals.at [213.229.14.34]) by svr1.postgresql.org (Postfix) with ESMTP id 04D0D8B9FB3 for ; Thu, 10 Feb 2005 00:55:07 +0000 (GMT) Received: from localhost (morework [127.0.0.1]) by morework.geizhals.at (Postfix) with ESMTP id 213B4DEE91; Thu, 10 Feb 2005 01:55:03 +0100 (CET) Received: from [10.0.0.33] (mjy.ghoffice [10.0.0.33]) by morework.geizhals.at (Postfix) with ESMTP; Thu, 10 Feb 2005 01:55:03 +0100 (CET) Message-ID: <420AB0E9.8070808@geizhals.at> Date: Thu, 10 Feb 2005 01:55:05 +0100 From: "Marinos J. Yannikos" User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Oleg Bartunov , pgsql-performance@postgresql.org Subject: Re: GiST indexes and concurrency (tsearch2) References: <4201AEB1.4000504@geizhals.at> <4202053B.10207@geizhals.at> <4204C3B4.1050209@geizhals.at> <24848.1107630092@sss.pgh.pa.us> In-Reply-To: <24848.1107630092@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 at geizhals.at X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200502/161 X-Sequence-Number: 10490 Tom Lane wrote: > I'm not completely convinced that you're seeing the same thing, > but if you're seeing a whole lot of semops then it could well be. I'm seeing ~280 semops/second with spinlocks enabled and ~80k semops/second (> 4 mil. for 100 queries) with --disable-spinlocks, which increases total run time by ~20% only. In both cases, cpu usage stays around 25%, which is a bit odd. > [...]You said > you're testing a quad-processor machine, so it could be that you're > seeing the same lock contention issues that we've been trying to figure > out for the past year ... Are those issues specific to a particular platform (only x86/Linux?) or is it a problem with SMP systems in general? I guess I'll be following the current discussion on -hackers closely... Regards, Marinos