Conversation
Contributor
Benchmark Results
Median of 10 attempts (* = outlier, excluded from result), 5000 iterations x 10 rounds, 33.27s total |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The scenario
Running
php artisan view:cachetakes significantly longer (~4s with Blade vs 1 minute and 20 seconds with Blaze)The problem
Blaze's compilation path wasn't optimized to the same degree as its rendering path.
The solution
ComponentSourceinstances — avoiding redundant disk reads and directive parsing for the same component.PhpParser\Parseras a singleton — instead of constructing a new one on every parse call.view:cachein Laravel — laravel/framework#59145.These changes brought compilation time on the same demo app from 1m20s down to ~4s.