Jump to content

-sandro-

New Members
  • Posts

    8
  • Joined

  • Last visited

    Never

Profile Information

  • Gender
    Not Telling

-sandro-'s Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. I'm a little confused about fast_cgi though if the script duration is controlled in php.ini what do these exactly control?
  2. My point was: if the threaded system is MUCH better in terms of RAM used why not use this on Linux and by default? I'm able to serve 250 concurrent connections with 120MB used for what on Linux requires to just start 15 children processes!
  3. Hi all! I have Apache + mod_php installed on Windows but I can't "relate" it to any of those used on Linux. It only has this: regarding the children. httpd.exe only takes 12MB of RAM and if I do an "ab" test with a script with only sleep(10) with 30 concurrent connections it only goes to 30MB of usage and it can take all of them together! I did the same on my ubuntu vps also in mod_php and to get 30 concurrent connections I had to start 30 servers and the VPS basically crashed because the RAM usage went over 200MB for the apache processes only. So the question is why the RAM used is -so- little?
  4. It's not something easy that you could do on your own on cheap services something like this could help http://edgedirector.com/ edit: and this http://www.dnsmadeeasy.com/
  5. looks very odd to me, maybe you're not using an absolute path in the include function? But that doesn't explain why php doesn't show any error if it can't find the file just an attempt try to change nginx settings like this fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; I remember that when the config settings are wrong and you try to open a non-existent php file it will return a black page
  6. kicken a big THANK YOU. The reason why things didn't add up for me is because on Windows things are completely different. In the documentation I found: This explains why with apache and mod_php setting the timeout to 0 I could run scripts non-stop! So I suppose there's no way to overwrite the limit for fast_cgi directly in the script right? The only way is to launch scripts in CLI?
  7. how to handle timeouts with PHP in php5-fpm + ngnix configurations? I tried to make a simple script with just sleep(60); php.ini max_execution_time = 30 fast_cgi fastcgi_connect_timeout 60; fastcgi_send_timeout 50; fastcgi_read_timeout 50; The script stops at 50s for timeout of the backend. What do I have to do to [*] enable the max_execution_time in php.ini [*]enable ini_set to change the execution time to 0 directly in the script Why does fast_cgi get to control timeouts over everything instead of php itself?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.