Bug #15746 Updated: Process exec() is slow from webserver - running from shell is ok ...
| From: | gallery at bianco dot net | Date: | Sun, 21 Jul 2002 08:51:34 +0000 |
| Subject: | Bug #15746 Updated: Process exec() is slow from webserver - running from shell is ok ... | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-14722@lists.php.net to get a copy of this message | ||
ID: 15746
Updated by: gallery@bianco.net
Reported By: nigel@green-bean.com
Status: Feedback
Bug Type: Performance problem
Operating System: Windows 2000 Server
PHP Version: 4.1.1
New Comment:
Win32 - Full netpbm dist runs at acceptable speed.
Was able to fix problem by swithing to full netpbm release (10.5). I
only experience the idle CPU problem with the netpbm-gallery 1.1
release, distributed on the gallery site. So it may not be a PHP exec()
bug after all.
In order to use the full netpbm dist, I needed to make changes to
Gallery's config.php:
Change:
$gallery->app->pnmtojpeg = "ppmtojpeg";
To:
$gallery->app->pnmtojpeg = "pnmtojpeg";
ppmtojpeg.exe does not exist in netpbm 10.5.
Chris
Previous Comments:
------------------------------------------------------------------------
[2002-07-19 15:21:16] nigel@green-bean.com
Jon (jonohlsson@hotmail.com) was able to get Gallery and NetPBM running
with a mixture of binaries (v10.3 of NetPBM). I had him zip up his
installion so I could see if this worked for me. It did not - I still
have the same issue as everyone else.
Nigel.
------------------------------------------------------------------------
[2002-07-19 15:18:24] gallery@bianco.net
Winnt4 sp6
Apache 1.3.26 (win32)
PHP 4.2.1 (win32) (exe timeout set to 300sec)
Gallery 1.3
netpbm-gallery 1.1 Microdist
Celeron 466/196MB
I am experiencing the same slowness using gallery's PHP scripts to call
the netpbm binaries. Each 1.2 MB image takes about five minutes to
have a thumb and resized version created. At first I thought it was
due to the celeron, but after watching TaskMan, the netpbm exe's are
idle most of the time.. they take available CPU once every few
minutes.. Something is causing a wait/timeout in the process.
I am not behind a firewall, so Im not sure that is the issue. It is
possible that using the netpbm/gallery microdist is causing the
slowness. I have been unable to get the standard netpbm dist working.
Thanks,
Chris
------------------------------------------------------------------------
[2002-07-17 04:36:02] jonohlsson@hotmail.com
Other interesting facts: the problem previously was time-outs. Every
added jpeg took like forever to upload. but if you studied the
taskmanager there was a pattern. Every jpegtopnm.exe call was idle (cpu
0 %) for about 30 secs...then the cpu jumped to 100% for about 1 sec.
So there must have been some 30 sec parameter somewhere making the call
rest. I dont know: I've checked every parameter there is in php.ini and
congig.php (for gallery) and httpd.conf. Could it really be a
firewall-issue...? ...it feels strange..BUT alas it works now.
/jon
------------------------------------------------------------------------
[2002-07-17 04:26:53] jonohlsson@hotmail.com
Well Im running PHP 4.2.1/Apache 2.0.36...I didn't download that
php_win32_latest.zip because after some further tweaking IT STARTED
WORKING!
I really cannot reconstruct any detailed info about what I did but now
I can upload jpegs really fast. Every jpeg-image takes about 1 sec.
I think I used the latest netpbm release (10.3) and then I may have
used the jpegtopnm.exe from the 9.25 release (not sure). I used the
cyg*.dlls from the 9.25 release though. At first there was no
improvement BUT THEN I TURNED MY NORTON FIREWALL OFF AND VOILA...IT
STARTED WORKING LIKE 'SNAPPING YOUR FINGERS'.
Sorry I cannot be of more help...if you like i could zip all files im
using for you to analyse...
/jon
------------------------------------------------------------------------
[2002-07-16 14:23:19] sniper@php.net
Try this snapshot first:
http://snaps.php.net/win32/php4-win32-latest.zip
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/15746
--
Edit this bug report at http://bugs.php.net/?id=15746&edit=1