fix(app): reuse computed runtime config across requests #2575
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.
π Linked issue
#2569
β Type of change
π Description
In our Nuxt application, we noticed that as the size of the runtime config the performance decreases significantly. Loading the runtime config occurs in every request and was making up a significant portion of the request time. Since there is not a need to recompute the config every request, we created a plugin to load the config at startup instead of for each request.
But I think this performance improvement would also be beneficial for other Nitro users and would make sense in core. Unless my assumptions here are wrong. Perhaps in that case, it could be configured?
I've done some very rough tests with autocannon against a cached page to show the impact we're seeing. It's nearly twice as fast in the average case.
Before Change
After Change
π Checklist