Thanks Artur,
I was testing this only on dev machine without opcode cache and I
confirm all your conclusions:
- without opcode cache is slower than with normal autoloaders
- with opcode cache is faster than normal autoloaders
- it consumes more ram than normal autoloaders
Cristian
On Mon, Oct 15, 2012 at 1:03 PM, Cristian Bichis <[email protected]
<mailto:[email protected]>> wrote:
Anyone has an idea why the classmap autoloaders are so slow?
They will almost always be slower without opcode cache (like APC), but
will be faster
that path-based loader with opcode cache. They are fastest with scale
and complex
loading structures (i.e. many components with plugins, many modules
scattered
across directories).
They will always consume more memory because the array of paths has
to be loaded
and held there. With larger apps expect even 10-50 MB more mem usage.
The upside
is faster code execution and static files should be served without php
anyways.
--
__
/.)\ +48 695 600 936
\(./ [email protected] <mailto:[email protected]>
