-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
cache warmup missing in Composer\ScriptHandler in 4.5 #59
Comments
|
|
|
There still seems to be a difference. This is the state of And this is the state of the cache after annotations.map
+ annotations.php
appProdProjectContainer.php
appProdProjectContainer.php.meta
appProdProjectContainerUrlGenerator.php
appProdProjectContainerUrlGenerator.php.meta
appProdProjectContainerUrlMatcher.php
appProdProjectContainerUrlMatcher.php.meta
+ bundles.map
Container2y5l8mc/
contao/
+ pools/
templates.php
+ twig/Furthermore, this is the average response time for the first request after
And this after
The latter provides an over 144ms better result. |
|
That's interesting. Which commands exactly did you run? You should compare
to
|
|
I've tested the following way: and I did this before each request to ensure consistency. I did it 5 times for each case and took the average response time. Note: I have used |
|
What is the content of the |
|
The content of Btw., when using The
|
|
Hm, that does not make much sense, does it? Both |
|
Can you reproduce it? May be it only occurs on Windows? I'll also try on a Linux machine. |
|
I was actually unable to reproduce this on a Linux based shared hosting environment... |
|
Yes I can reproduce it. But both |
|
Anyway, we should probably just re-add the |
|
And |
|
Yes. Basically the code from Contao 4.4. manager-bundle/src/Composer/ScriptHandler.php Lines 37 to 38 in df75e03
|
|
Fixed in 77c85e2. |
In version 4.5, the
cache:warmupwas removed fromIs there any particular reason why? This leaves the website in an inefficient state after a composer operation, if you do not manually run
The text was updated successfully, but these errors were encountered: