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 EF96AD1B16A for ; Fri, 23 Jul 2004 12:34:25 -0300 (ADT) 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 89176-10 for ; Fri, 23 Jul 2004 15:34:19 +0000 (GMT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by svr1.postgresql.org (Postfix) with ESMTP id 67DFCD1B25F for ; Fri, 23 Jul 2004 12:34:18 -0300 (ADT) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail1.panix.com (Postfix) with ESMTP id 5575F48912 for ; Fri, 23 Jul 2004 11:34:17 -0400 (EDT) Received: (from adler@localhost) by panix2.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i6NFYHE20075 for pgsql-performance@postgresql.org; Fri, 23 Jul 2004 11:34:17 -0400 (EDT) Date: Fri, 23 Jul 2004 11:34:16 -0400 From: Michael Adler To: pgsql-performance@postgresql.org Subject: Re: Performance over a LAN Message-ID: <20040723153416.GC8970@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/153 X-Sequence-Number: 7544 On Fri, Jul 23, 2004 at 03:20:54PM +0930, William Carney wrote: > But with the server running on one machine and the client running on > another, the two machines being connected by a 100 Mb ethernet, with nothing > else on the network, this test takes 17 minutes to run. I have tried > changing the frequency of COMMIT operations, but with only a small effect. > > The machines used are P4s running FreeBSD 5.2.1. The Postgres version is > 7.4.3. Can anyone tell me why there's such a big difference? Can you reproduce this problem in a tiny test case? If your application is doing other networky things (e.g. many name resolutions that hang for 10 seconds each), they may be slowing down the PostgreSQL work. Just a WAG. -mike