Okay big thanks again, Stefan. I changed the Network timeout to 125 and the FastCGI to 120.
I also upped my Linode to 1GB ram. Im running aggregators on Drupal and sometimes they take a long time to finish. I will hold off on the php-fpm until things occur again. Much fine appreciation for this assistance! Thank you! --Hans On Mon, 14 Nov 2011 03:57:17 +0100 Stefan de Konink <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Op 14-11-11 03:41, [email protected] schreef: > > Hi and big thanks! :) > > > > I have increased Spawning timeout to 10 already and have set > > PHP_FCGI_CHILDREN to 15 (and fyi - before migrating to php-fpm I > > am still am getting 504 on the Cherokee admin pages -- I am on a > > Linode w/ 512 RAM). > > 15 here means: 15 users can concurrently use PHP. So if 15 users use a > heavy search function on your site. The 16th has to wait and might get > a timeout. > > php-fpm can 'theoretically' scale the amount of children dynamically, > but can't get you the magic memory for it. And with PHP you will need > memory. > > It is also possible that your php script is just to slow (for example > takes longer than 15 seconds to compute). This will also result it > issues. This is another timeout, you can find it in the FastCGI > handler setting go to Tab Restrictions. You might increase that, but > keep it below the network timeout. (Found in General: Timout) > > > > Is this a correct way to migrate to php-fpm? > > No clue, but it looks ok. > > > Stefan > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.18 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEAREKAAYFAk7Ag4wACgkQYH1+F2Rqwn30+QCffVWpe4uOTS4WWh6iH+Ws5QCU > 3rEAn2/Lhtuff1c9nkhzXpS/QEGMQWfB > =2KNE > -----END PGP SIGNATURE----- _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
