From: | Robby Russell <rrussell(at)commandprompt(dot)com> |
---|---|
To: | A Palmblad <adampalmblad(at)yahoo(dot)ca> |
Cc: | pgsql-php(at)postgresql(dot)org |
Subject: | Re: PHP memory usage |
Date: | 2004-06-02 20:17:51 |
Message-ID: | 40BE35EF.8030003@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
A Palmblad typed this on 05/31/2004 02:22 PM:
> We've been running into some issues with PHP and Postgres, and memory usage.
> On a dual athlon 64, w/ 4 gigs of RAM, PHP 4.3.6, and Postgres 7.4.2 I've
> seen our server start to crawl after some queries returning very large
> result sets. Although large result sets aren't exactly what we want to be
> dealing with, I really want to avoid a situation where a user could disrupt
> our server with certain options to some searches.
>
> I did a quick commandline test, and it looks like PHP starts to eat memory
> during its call to pg_query. By eat memory, I mean use memory well in
> excess of php.ini's memory_limit of 8 megs. (I stop it around 90% of
> available memory usage) Is this acceptable behaviour, or should I report it
> to PHP as a bug? If not, are my only solutions to wrap my selects in
> cursors and/or to use limit?
>
> -Adam Palmblad
>
I am going to take a quick guess and suggest that test those queries in
psql itself. You might be running into some issues with your queries.
Test your queries with psql, EXPLAIN.
\h EXPLAIN
-Robby
--
Robby Russell, | Sr. Administrator / Lead Programmer
Command Prompt, Inc. | http://www.commandprompt.com
rrussell(at)commandprompt(dot)com | Telephone: (503) 667.4564
From | Date | Subject | |
---|---|---|---|
Next Message | A Palmblad | 2004-06-02 20:41:33 | Re: PHP memory usage |
Previous Message | Nick Barr | 2004-05-31 22:50:43 | Re: PHP memory usage |