-
-
Notifications
You must be signed in to change notification settings - Fork 436
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
Remove "compiler" related code #525
Comments
Referring Alan Storm article 2011: I think since 2011 PHP performance was so increased that searching for M1 files in separate directories is no more a bottleneck. I don't remember where to find the reference but some time ago I've read a benchmark showing that M1 compiler has no effect in PHP7. |
a big part of this improvement is because of the OpCache, which additionally caches file access so effectively, that the number of files became not relevant for PHP anymore |
+1, remove it to prevent use |
just for a reference, long time ago together with Fabrizio we've developed an extension which caches autoloaded paths, as an alternative for the compiles https://github.com/AOEpeople/Aoe_ClassPathCache |
+1 |
👍 |
For Years the Magento1 Compiler code is mostly unused and recommended against to use it.
To reduce Code/Logic (and because someone suggested it) I would like to see the Compiler related code be removed (maybe leave empty methods, in case its needed for compatibility reasons?)
What are your takes on this?
Context what it is:
https://magento.stackexchange.com/questions/179093/what-is-compilation-in-magento-and-its-use
and prove I have prejudice here:
https://magento.stackexchange.com/questions/12996/when-should-i-use-the-magento-compiler/15204#15204
The text was updated successfully, but these errors were encountered: