We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What is the performance impact of the runtime check combined with yield ?
Originally posted by @stof in #3999 (review)
Hello,
While investigating a performance regression in a symfony app (6.4) I found that the source was twig/twig version 3.9.0.
I made a small repro and used git bissect to find this pull request #3999 where performance is briefly discussed.
After some trial and error, performance was partially restored by passing 'use_yield' => true to the twig Environment constructor.
'use_yield' => true
Not sure if this is a bug but in certain cases the performance impact was pretty huge (from 800 ms to 2200ms).
The text was updated successfully, but these errors were encountered:
Probably related to this discussion I opened a few days ago
Sorry, something went wrong.
No branches or pull requests
Originally posted by @stof in #3999 (review)
Hello,
While investigating a performance regression in a symfony app (6.4) I found that the source was twig/twig version 3.9.0.
I made a small repro and used git bissect to find this pull request #3999 where performance is briefly discussed.
After some trial and error, performance was partially restored by passing
'use_yield' => true
to the twig Environment constructor.Not sure if this is a bug but in certain cases the performance impact was pretty huge (from 800 ms to 2200ms).
The text was updated successfully, but these errors were encountered: