-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.0] Optimising Composer Autoloader #16881
Comments
It might be better off in 4.0 than 3.x. Honestly the only difference it makes as it relates to code is it adds each class individually to the class maps in Composer's |
As we have only external packages loaded trough composer, guess it will be worth a try to run it in optimized mode. |
From https://getcomposer.org/doc/articles/autoloader-optimization.md#trade-offs:
So from what I understand, Level 1 optimisation should be done as there is no reason not to do it. Level 2 is another topic and doesn't look like suitable for us. |
I was playing around with it and it creates bigger classmap files. Created a pr for it #16896. I think it is worth to enable it, even tough in staging the impact will be little, but in J4, where we have more libs installed, we will get some improvements. |
Closing as we have a PR :) |
Honestly I have no clue if we do that already or not or if it is even something we should or could do.
I just stumbled over the composer option
optimize-autoloader
(see https://getcomposer.org/doc/articles/autoloader-optimization.md). According to that doc this option should be activated for production enviroments as it speeds things up quite a bit.What do you composer savvy guys think?
The text was updated successfully, but these errors were encountered: