So far I haven’t encoutered that error since I’ve been using XAMPP on both windows and ubuntu OS

you must be running a pretty complex script. unless you’re generating a big report, the 60 seconds execution time limit should be enough. Try optimizing your script a little, or use 3rd party extensions like eAccelerator. I think XAMPP has eAccelerator bundled.

BTW, nice blog.

Hi Pao,

For this case, i think something like eAccelerator will not help. it’s not helping because am running a bot from a third party.

what else can i do?

hi cai

in general, it’s bad to resort to modifying php.ini just because you can’t make your script work or run fast. global configuration file kasi yung php.ini, in real life situations may mga iba pang php scripts na tumatakbo sa server aside from your own scripts, if you just modified php.ini then maaapektuhan din sila, baka magkaroon pa ng bad consequences for those scripts…(assuming that you even had the permission to modify php.ini)

kung nagta-timeout yung php script mo, i suggest i-check mo muna kung may problem sa mga for/while loops mo, baka yun ang kailangan mong i-optimize muna. kung wala, then check mo kung mabagal yung site na fine-fetch ng curl call mo. in that case, adjust mo yung timeout ng curl call mo (try “curl_setopt($ch, CURLOPT_TIMEOUT, $new_timeout), etc”), wag mong patagalin mag-execute yung curl functions mo. puwede ka rin gumamit ng caching techniques (Cache_Lite pear module, etc).

then if after you’ve done those eh nagta-timeout pa rin ang mismong script mo, i suggest gumawa ka ng “.htaccess file” sa directory ng script mo, tapos lagyan mo ng ganitong entries:


php_value max_execution_time 300
php_value max_input_time 300


that way, yung script mo lang ang maaapektuhan.

@perryv - thanks for the info but yeah, nimodify ko na. binalik ko na ung original na timeout sa ini files kasi i realized the same thing na sinabi mo.

hindi si curl ung may problema, i have 200 - 400 curl calls kaya mahaba ung hinihintay ni php script, kaya ang ginawa ko nagset na lang ako using set_time_limit() para sa concerned script lang.

ah, 200 to 400 curl calls ba? akala ko “20 to 40″ curl calls lang (see your Edit: paragraph on your post). super dami ah?

captcha: blare

by the way, mas maganda yung solution mo using set_time_limit(), no need to mess around apache’s config files.

captcha: heard

thanks perryv

bad program design creates memory intensive calls. basically you rarely need to modify the config file ,running cURL on the command line and
firing curl requests in parallel will be the best approach have fun

next code please!

Si Dimaks naghahanap na naman ng bagong post, hahahahaha