Why use a PSR-0 or PSR-4 autoload in composer if classmap is actually faster?

by

The problem is that the classmap is NOT actually faster in every case!

The speed of the classmap comes from not having to check the filesystem if a file exists before doing the always necessary work of loading it, parsing it (opcode caches will help here) and then executing it.

But the downside of the classmap is that you possibly generate a huge amount of data for every single class, interface and trait included in the libraries you use, without you actually using it in your production code. Loading huge arrays does not come for free – while the code need not be parsed again and again (opcode cache), it still has to be executed, the array data structure has to be put into memory, filled with lots of strings, and then eats up some amount of memory that might have been usable for something else.

I found two resources discussing this topic: First of all there is github issue #1529 suggesting further improvements for the composer autoloader using a bunch of symlinks to avoid having to scan multiple directories.

The discussion there also reveals that you should actually try to use the best possible namespace- or classname-prefix in the PSR-0 autoload declaration, i.e. the longest one possible. You can also use more than one prefix in the declaration.

Then there is a blog post linked in that issue that documents some xhprof benchmarks using a stock EZPublish 5 and fiddling with the settings, including APC Caching and classmap dumping.

Money quote:

This command created a 662KiB vendor/composer/autoload_classmap.php file containing an array that is a hash composed of the class name as index and the path to the file containing the class definition as value. At the time I am writing this post, this array is composed of 4168 entries.
[…]
Although it should give us the most efficiant autoloading mechanism, it actually slows things down (from 254.53 reqs/second to 197.95). The reason being that even if the file is cached by APC, the PHP array containing the map with more than 4100 entries needs to be re-created at every single request.

Will a classmap be fast? Certainly. Fastest in every case? Of course not – it depends on the ratio used vs. unused classes per request. So even if on average your application actually uses ALL classes in the map, a classmap might still be slower if you only use about 10% of the classes per request, and you’d be better off optimizing the autoload declarations of the libraries you use. In fact, every classname prefix should only ever point to exactly one directory.

Note that the performance gain you’d achieve only is in the area of about low single digit milliseconds per request. Your application surely is awesome if that figure is a significant performance boost in the range of 5 to 10%. But if you really are in that performance range, blindly believing that a classmap is ALWAYS faster probably wastes a lot of unnecessary CPU cycles.

If you optimize something: Measure it! How would you know if it actually becomes better if you cannot measure it?

More Related Contents:

  1. How to create a PSR-4 autoloader for my project?
  2. What Are the Differences Between PSR-0 and PSR-4?
  3. Class Foo\Bar\Baz located in ./foo/bar/utility/baz.php does not comply with psr-4 autoloading standard. Skipping
  4. Autoloading classes in PHPUnit using Composer and autoload.php
  5. Using Composer’s Autoload
  6. PHP adding custom namespace using autoloader from composer
  7. PHP – most lightweight psr-0 compliant autoloader
  8. How to use Composer to autoload classes from outside the vendor?
  9. Reference – Composer error “Your PHP version does not satisfy requirements” after upgrading PHP
  10. How to install a specific version of package using Composer?
  11. Composer update memory limit
  12. How do I use PHP namespaces with autoload?
  13. How do I install Composer on a shared hosting?
  14. Tell Composer to use Different PHP Version
  15. How to use spl_autoload() instead of __autoload()
  16. requires ext-fileinfo. How do I add that into my composer.json file?
  17. Change PHP version used by Composer on Windows
  18. You must enable the openssl extension to download files via https
  19. Composer killed while updating
  20. Composer Update failed — out of memory
  21. How to add private github repository as Composer dependency
  22. How to change PHP version used by composer
  23. PHP error: “The zip extension and unzip command are both missing, skipping.”
  24. Composer/PSR – How to autoload functions?
  25. PHP Composer update “cannot allocate memory” error (using Laravel 4)
  26. Composer cannot download files
  27. Composer running out of memory on every project, Mac OS X
  28. What is autoload in php? [duplicate]
  29. but these conflict with your requirements or minimum-stability
  30. Class Firebase\JWT\JWT not found

Leave a Comment