Re: Using the pear installer (or pyrus) as an applicationdeployment tool

Stephan Wentz wrote: >> An alternative to this would be to distribute the contents as a phar >> which would preserve everything and prevent inadvertent modification. > > Phar was my first thought, too. But with that many components (and thus, > phars) my tests really didn't produce very good performance - it was > something like 3 times slower. APC was enabled, I didn't look deeper > into this and why it's getting so slow. > Did anyone here in this group run some tests with lots of phars (not > only one)? Did you try enabling phar.cache_list? http://us.php.net/manual/en/phar.configuration.php#ini.phar.cache-list That tends to make performance much better, although it won't match APC outside of a phar, because all files must route through PHP and phar, losing some of the webserver efficiency. Greg