Optimize logger by creating single pino instance at module scope #31
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 logger was creating a new pino instance on every log call (
buildBaseLogger()invoked in each function), causing unnecessary memory allocation and instantiation overhead.Changes
buildBaseLogger()function with module-scopedloggerconstantloggyInfo,loggyDebug,loggyWarn,loggyTrace,loggyFatal,loggyError) to reference shared instanceloggyRequestReceivedBefore:
After:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.