slow "time to first byte" on logged in state #682
Conversation
This file contains 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
added 2 commits
August 17, 2016 16:12
When the user is logged in the browser measure for time to first byte is very slow (1.5s). I am testing with a remote mongodb which might contribute to the issue. In that situation also responses for js-files, assets and css all suffer the same initial delay. My debugging brought me to the conclusion that the handleOnAllRoutes has some side effect that is causing this. I do not see a reason why handleOnAllRoutes would need to run on every request and especially for static files / assets? Therefore i wrapped the call to handleOnAllRoutes into the picker route when we are anticipating an html rendering to occur.
travis build failed due to trailing whitespace
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
When the user is logged in the browser measure for time to first byte is very slow (1.5s). I am testing with a remote mongodb which might contribute to the issue. In that situation also responses for js-files, assets and css all suffer the same initial delay. My debugging brought me to the conclusion that the handleOnAllRoutes has some side effect that is causing this. I do not see a reason why handleOnAllRoutes would need to run on every request and especially for static files / assets?
Therefore i wrapped the call to handleOnAllRoutes into the picker route when we are anticipating an html rendering to occur.