It would require them going out of their way to make winston blocking, and serve no purpose.
As their tagline says "async logging library". No, winston is not blocking. Though, note that as with any piece of code, it adds onto the CPU. If you log in high impact sections of code and pass meta values, it could spend a significant amount of time to process the logs and the util.inspect calls on meta will add up. So unless you're logging in a hot section of code and using meta, don't prematurely optimize. On Wednesday, July 15, 2015 at 7:53:01 AM UTC-4, Sac King wrote: > > Hello, > > I am working on a application, using winston nodejs as logging framework. > I have a doubt, whether winston logging is blocking my application thread ? > As we know node is single threaded, i have put a debug statement using > winston and using File transport for it. I want to know whether, will it > affect on my application performance ? > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/83dc1177-a772-4b39-b8e3-96eff48a56d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
