I'm 👎 on putting DataCollector namespace into a class cache because they are dev environment only.

This is problematic.

As soon as you add a class that might be extended, or implemented, and someone reads annotations from that class (for example like JMSDiExtraBundle does), you'll have a significant slow down.

I'm wondering how much we gain by adding these classes? In my experience, this is quite insignificant as soon as you use an op code cache.

@schmittjoh comment is important: the slow down comes from the fact that the annotation reader will then have to parse the cache file (which, by definition, is huge). That's why some of the classes were not added before. We cannot just add classes to the cache blindly, that must be an iterative process.

Another idea might be to make this a deployment only feature in which case we could be more aggressive. For dev environment, you probably do not care about the small speed increase anyway.

@fabpot comments are stripped now I think.

Some other remarks: we should not add debug classes, the added class hierarchy & interfaces are automatically added so there might be some extra things added here.

@ALL you are right but then there's the following issue :)

• Download 2.2 RC2 zip from the website.
• unpack the archive into two different folders: sf22rc2_ori sf22rc2
• apply this patch to sf22rc2
• run /app.php/
• notice the classes loaded using APC, it should be something like this

I'm not saying that this solves the problem. It just shifts the problem from the autoloader, which doesn't need to load 150+ classes anymore but only 30+ and brings the performance back to more acceptable levels.

The problem that the debug classes are still used in production environment should be a good thing to debug/fix but I won't have time for this until the weekend comes.

I've been saying that Symfony 2.2 has a major speed regression for almost two months now and I know that my Symfony skill is not as good as yours guys but maybe you could help me out a bit on this.

3% speed decrees is not good for some people, currently we are at ~25%+.

I've did benchmarks for every change related to speed and I've provided links and documentation on how to replicate the issue. I'm willing to do all the work needed to fix the issues related to this but please read my previous comments before saying that this might not help much or it doesn't work and so on.

Or if you know how to make the current situation better, please go ahead, close this, open a new issue which says what needs to be done or a PR with the needed changes and I'll gladly test and changes or help out in any way possible.

Thank you.

The above run /app.php/ should read: run /app.php/ 3-4 times then proceed to next step

@dlsniper sorry if I can't help right now but as you should know we have other horses to fight here in france atm.

Closing.