admirau wrote:
Doctrine provides nice option to compile most important classes
into one big file, stripping comments etc.
to reduce server operations.
This option for ZF would be nice.
That is not a technique we generally suggest for a performance improvement.
Ideally, you could be using an op-code cache. Op-code caches will do
"under the hood" what you are looking to do by compiling source into one
large file (basically reducing the number of file stats, and loading
pre-compiled code into the applications runtime).
Also have a look at the performance guide:
http://framework.zend.com/manual/en/performance.html
I noticed also that Zend_Tool
creates index.php with configuration
and the same file runs the application.
It would be good to have ability to include
configuration only if it is needed somewhere else
eg. in php cli or phpunit.
We are still exploring this use case to fully understand what is and
could be shared by the specific environments (web app vs. command line
tools vs. unit testing). At current, its probably best to have separate
ini files (or sections within the ini) for each environment so you can
specific what is needed for each. This also means that each environment
might need its own Zend_Application object and/or bootstrap object to
ensure that the expected resources are setup.
-ralph
