Non-blocking logger about picologging

[tonybaloney]

Great question, I'm still working on the basics for this library, but one of the first production use cases is an async worker and the reason I started this project is because the standard library logging module causes such an overhead.

I'll have a think about this next and update the thread

[tonybaloney]

Looking at the stdlib implementation, it was added in Python 3.2. I'd probably do it differently today. It's using pickling/copy.copy for thread safety and a worker thread, but a single one.

Firstly adding an async Handler and Logger specification, with a coroutine for .info(), .warning() etc. and then using an internal asyncio queue to write records and then sending those to the handlers in a worker thread, or within the coroutine. There are async stream writers for the outputs of the handler, so it would implement coroutines from top to bottom.

This library only supports Python 3.7+ anyway.

Not sure on the performance gains/losses compared to the queue, listener and worker thread approach.

What do you think?

[tonybaloney]

Try 0.6.0, it comes with a queue handler and listener. I'm working on the async stuff later

[Goldziher]

Great. I'd gladly contribute as well when there is more clarity

[Goldziher]

Sounds good. I also don't know about the performance differences, but I would assume that an async approach would scale better .