high-traffic php-sites often run out of file
Maybe one can make an algorithm that
internally converts a PHP-Project with many
includes into one big php-mmcache-bytecode-file.
So the number of open files per process
could decrease dramatically resulting in
a better ability for many parallel tasks!
Sure the price would be more cache-memory
consumption because every single file would
then contain all the includes that are normally
127.0.0.1/start.php is requested.
but start.php has to include 6 files.
That makes a total of 7 open files per request.
if one could compile all the 7 files to one automatically,
that would be a good advantage with respect to
the open file limit and the issue that the
open-file management decreases very fast the system
performance the more open file handles exist.