>> seems you're flying too high. >> RHEL5 still ships php5.1.6 and it has this option and it undefines >> ZEND_USE_ZEND_ALLOC. > > PHP 5.2.0 has been released more than 2 (two) years ago, which should be > enough for a distro to catch up, don't you think so?
Perhaps. But what they ship with RHEL5 is up to Redhat. >> For the newer versions (5.2.x) it can be set at the environment, which is >> not that good btw. > > Please elaborate. Ok. With default memory allocation strategy I can run relatively short scripts very efficiently and that's why I'd not change it for the web site. On the other hand, for long-running scripts that I run using php-cli, I'd always prefer resource saving priorities. In particular, I'd prefer ZMM not to "cache" memory blocks. With only one system-wide setting, I have no choise. Either all php will use ZMM or neither. >>> That won't affect memory usage very much. >> >> I gives appox 2MB per php-cli instance. Sometimes it's good enough, if >> for >> example you need to run 200 instances. > > Shared libs are, well, shared among the processes, so I don't think it's > "per instance". That's truth. Code segments will be shared. But even with 2MB of code, CPU uses 512 entries in TLB for _each_ process and it's clear worthless stuff. In case of hundred instances running simultaneously, it may save some time. Also, please add time for the initialization of the modules that won't be used. Anyway, if php is to be recompiled from the sources in order to build long-term running daemons, the configure options should be carefully tuned. -jv -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
