From: | "Mitch Vincent" <mitch(at)venux(dot)net> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Speaking of fulltextindex... |
Date: | 2000-06-23 19:46:13 |
Message-ID: | 00dd01bfdd4c$d39e8ea0$0300000a@doot.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrés Mauricio Marín Restrepo | 2000-06-23 22:03:35 | HI! Problems with cursors into triggers |
Previous Message | Jeff MacDonald | 2000-06-23 18:53:45 | query failed , don't know why |