From: Mitch Vincent <mitch@venux.net>
To: pgsql-sql@postgresql.org
Subject: Speaking of fulltextindex...
Date: Fri, 23 Jun 2000 15:46:13 -0400
Message-ID: <00dd01bfdd4c$d39e8ea0$0300000a@doot.org> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: mitch@venux.net
Subject: Re: Speaking of fulltextindex...
In-Reply-To: <00dd01bfdd4c$d39e8ea0$0300000a@doot.org>
References: <00dd01bfdd4c$d39e8ea0$0300000a@doot.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox