From: Chris Ruprecht <chrup999@yahoo.com>
To: Chadwick Rolfs <cmr@shell.gis.net>
Cc: PostGreSQL PHP Group <pgsql-php@postgresql.org>
Subject: Re: pg_pconnect - ??
Date: Mon, 28 Jan 2002 15:31:00 -0600
Message-ID: <p05101219b87b70bd3c70@[192.168.0.6]> (raw)
In-Reply-To: <Pine.SOL.3.96.1020128160529.25035E-100000@shell.gis.net>
References: <Pine.SOL.3.96.1020128160529.25035E-100000@shell.gis.net>
I usually have a page which connects, does some processing and
disconnects - very simple stuff. The user runs a number of queries
when she creates some invoicing, but it's always a matter of "1. load
page where to enter parameters; 2. execute the script which creates
the bill from the parameters; 3. return to step 1". Each invoice is
created individually - the user only has a few clients (big amounts
per bill, few bills).
The most traffic the user creates is when they change their rate
table, they might add 20 to 50 rates at per week. I could run that
stuff of an old 100 MHz Pentium with 16 MB RAM, if I had to and they
would probably not see and performance issues. However, some of the
bills they have process 500'000 line items at a time, this is where I
need the horsepower - but at that stage, the connection is already
made. The query runs across 4 tables and sometimes takes up to 4
minutes.
Best regards,
Chris
At 16:07 -0500 01/28/2002, Chadwick Rolfs wrote:
>Sorry, I guess you can disregard most of my reply:)
>
>But a functiont that checks for connections and makes on only if one isn't
>already there is still good idea, if you are making many queries in a
>small amount of time.
>
>Are you making many queries at once, or the same one many times, or
>different ones quickly?
>
>On Mon, 28 Jan 2002, Chris Ruprecht wrote:
>
>> Ok, so from what I see on here, pg_pconnect doesn't have any
>> advantages over pg_connect in my situation. I have the web server
>> running on the same machine as the database server and yes, I have
>> allocated 16384 shared buffers (at 8 KB each, this is 128 MB of
>> shared memory). I have not noticed any connect overhead when opening
>> a web page which connects to the database (99% of them do), the
>> connection is instantaneously, so I guess, I don't need to do
>> anything here.
>> I was under the impression, that a persistent connection would open
>> one and only one process which then will be used all the time without
>> creating more child processes which keep lingering about. I guess, I
>> was wrong here ...
>>
>> Best regards,
>> Chris
>> --
>> Chris Ruprecht
>> Network grunt and bit pusher extraordinaÌre
>>
>> _________________________________________________________
>> Do You Yahoo!?
>> Get your free @yahoo.com address at http://mail.yahoo.com
>>
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 2: you can get off all lists at once with the unregister command
>> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>>
>
>Chadwick Rolfs - cmr@gis.net
>Cleveland State University - Student
>Music Major - The Holden Arboretum Volunteer
>Computer Programmer - Student Employee
>--*I finally found powdered water;
>I just can't figure out what to add to it*--
--
Chris Ruprecht
Network grunt and bit pusher extraordinaíre
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
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-php@postgresql.org
Cc: chrup999@yahoo.com, cmr@shell.gis.net
Subject: Re: pg_pconnect - ??
In-Reply-To: <p05101219b87b70bd3c70@[192.168.0.6]>
References: <Pine.SOL.3.96.1020128160529.25035E-100000@shell.gis.net> <p05101219b87b70bd3c70@[192.168.0.6]>
* 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