Speed up logging #7
Closed
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
When you are logging many requests, each call must perform as quickly as possible, adding caching to the timestamp generation speeds it up a little bit :)
|
It appears that under heavy load, all of the log messages printed in a 1 second period will have the same timestamp... Is that really acceptable for your application, @soluwalana? |
|
@rmg ask what I want to ask. Sorry @soluwalana, I cannot accept your change. |
|
My resolution for the logs didn't need MS precision, idea for the change was taken from NodeJS's library for HTTP server timestamps. :) |
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.
When you are logging many requests, each call must perform as quickly as
possible, adding caching to the timestamp generation speeds it up a
little bit :)