Edit report at https://bugs.php.net/bug.php?id=54098&edit=1
ID: 54098 Comment by: f...@php.net Reported by: marco at mimecom dot net Summary: Overly high defaults in config Status: Closed Type: Feature/Change Request Package: FPM related Operating System: Linux PHP Version: trunk-SVN-2011-02-25 (SVN) Assigned To: fat Block user comment: N Private report: N New Comment: it'll be backport to 5.3 when 5.3.7 will be released Previous Comments: ------------------------------------------------------------------------ [2011-07-05 17:05:41] f...@php.net This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. I didn't make my point on this :) patch have been applied and will default values for 5.4 and trunk. ------------------------------------------------------------------------ [2011-07-05 17:03:25] f...@php.net Automatic comment from SVN on behalf of fat Revision: http://svn.php.net/viewvc/?view=revision&revision=312957 Log: - Implemented FR #54098 (Lowered default value for Process Manager) ------------------------------------------------------------------------ [2011-07-02 13:54:55] f...@php.net See http://news.php.net/php.internals/53723 for updates ------------------------------------------------------------------------ [2011-02-25 08:37:39] marco at mimecom dot net Further arguing the low memory systems a bit: I commonly get myself a 512M slice to start development of a site. It's fast enough to develop on - and when time come to deploy, I'd ramp it up to something faster. So the low memory scenario is highly valid in my case. And even if we are not talking clouds, I think many places in the world would have low-memory hardware due to cost reasons. In the cloud, slices commonly start at 256M even - although even I feel it's too low. Compare to MySQL - a default install is tuned for the lowest common denominator as well, making sure it runs. The nice dining of large systems comes with a tuning dessert... ------------------------------------------------------------------------ [2011-02-25 08:25:13] marco at mimecom dot net Well, since the configuration is active - not commented out - I'd say it is pretty much a default. A default make install would run with this configuration without modifications. You are right that my statement of there being a lot of 1Gb servers out there is taken out of the air - but I run a few (and two with 512Mb - still snappy), I know they are cheap (and it gets pretty expensive when you try to run larger servers) so it's just my *suspicion* that they are common. In any case, since the settings effectively are a default per above, I'd much rather see the software underperform than bring servers down. One way to fix it would be to comment out that setting and not let php-fpm start unless you go configuring yourself. But do mention in that comment to crosscheck with php's memory setting. It took a giant jump from a default 16M to 128M, which is why I think these settings kill servers. Before, at 16M, 50 was actually great. P.S. I don't really know what prompted that jump above, but it's not my concern... I guess there were reasons for it. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=54098 -- Edit this bug report at https://bugs.php.net/bug.php?id=54098&edit=1
