Bug #9154 Updated: HTTPD Memory Utilization Spike
| From: | zeev@php.net | Date: | Thu, 21 Jun 2001 13:51:13 +0000 |
| Subject: | Bug #9154 Updated: HTTPD Memory Utilization Spike | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-57533@lists.php.net to get a copy of this message | ||
ID: 9154
Updated by: zeev
Reported By: cbenedict@synhrgy.com
Old-Status: Open
Status: Feedback
Bug Type: Performance problem
Operating system:
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Reassign status
Previous Comments:
---------------------------------------------------------------------------
[2001-05-08 19:25:33] zeev@php.net
Is this fairly reproducible?
If it is, any chance you could build Apache with debug information (--enable-debug in configure),
attach to an offending process (gdb /path/to/httpd <PID>), and run a backtrace
('bt')?
---------------------------------------------------------------------------
[2001-02-07 11:55:47] cbenedict@synhrgy.com
Using ezxmlrpc 1.0 library from ez systems to write web services. Ezxmlrpc uses the qtdom option to
process XML. Web services are reading from and writing to Postgres 7.0.3 database. Web services
are working properly, but when they are called repeatedly (anywhere from 6 to 25 times in a row),
one of the httpd processes eats all of the CPU and memory utilization spikes to over 100MB. PHP
interpreter eventually stops because max execution time of 30 secs is exceeded. Then, memory
utilization for that process drops back down to around 3MB.
I am using apache 1.3.14 and have php built as a DSO. I do not seem to get a core dump, so I can
not include a backtrace.
My configure line follows:
./configure --with-apxs=/usr/local/apache/bin/apxs --with-magic_quotes --with-dom --with-qtdom
--with-pgsql --enable-debug
I am classifying this as a performance problem, even though I know it is not. Don't know how
else to clasify it. I know this is not enough info to begin debugging this problem. Can someone
give me some tips on how I can narrow this down?
---------------------------------------------------------------------------
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=9154&edit=2