Received: from icebox.venux.net (icebox.venux.net [216.120.166.10]) by hub.org (8.10.1/8.10.1) with ESMTP id e5NJmP119575 for ; Fri, 23 Jun 2000 15:48:25 -0400 (EDT) Received: from doot (usr1-ip114-grr.wmis.net [209.176.193.164]) by icebox.venux.net (Postfix) with SMTP id 9C5312620B for ; Fri, 23 Jun 2000 15:54:38 -0400 (EDT) Message-ID: <00dd01bfdd4c$d39e8ea0$0300000a@doot.org> From: "Mitch Vincent" To: Subject: Speaking of fulltextindex... Date: Fri, 23 Jun 2000 15:46:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Archive-Number: 200006/215 I just noticed this in some testing.. When I use my PHP application to insert text into the field that's used in the full text index it takes 9 full seconds, when investigating resource usage using 'top' I see this : Development from a completely idle start up : PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 682 postgres 2 0 124M 2328K select 0 0:00 0.00% 0.00% postgres Production server -- this one is being used : PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 96825 postgres 2 0 38380K 35464K sbwait 0:04 2.10% 2.10% postgres The backend is started exactly the same way with the same version (7.0.2) on these two servers with the options -B 4096 -o '-S 16384' -- can anyone think of a reason why would one initially grow to 124 megs? I'm waiting to see about that before I continue investigating the sudden exponential increase in my INSERT speed - hopefully it's related (because I sure see why the transaction suddenly take ten times longer to complete than it did!).. Thanks!! -Mitch