#54990ClassLoader cache ist too slow, no matter which CF Backend is used
Description
while Profiling a 6.2 installation with XHProf I found that the most expensive part of the request is always the classloader cache – no matter which CF backend is used for it.
the attached callgraphs both show the delivery of a cached page, one with the default configuration (simple file backend) and one with the classloader cache Backend set to memcached.
In both cases we see that either file_get_contents() or Memcach::get() is the most expensive function.
the request times (mesured with the adminPanel) are almost the same in both cases: ~155ms with simple file backend and 150 ms with memcache
Since memcache should be way faster than the filesystem I think there’s a lot of room for optimizing in the classloader.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.