Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Console sink? #26

Open
petke opened this issue Oct 12, 2017 · 2 comments
Open

Console sink? #26

petke opened this issue Oct 12, 2017 · 2 comments

Comments

@petke
Copy link

petke commented Oct 12, 2017

(I have swapped from boostlog, to spdlog, to g3log, and now im using nanolog)

I like the simple interface of nanolog, but have lots of code that expects INFO and above logs to end up on console. How do I do this in nanolog?

@chengm349
Copy link

Petke,

spdlog and g3log, which better? according to your sequence, should be g3log. are u still using nanolog?

@petke
Copy link
Author

petke commented Dec 6, 2018

@chengm349

I'm still using nanolog. It works fine for me. Haven't touched my logging code in a long time, so don't remember the specifics anymore.

I was convinced of the benchmarks (https://github.com/Iyengar111/NanoLog#latency-benchmark-of-guaranteed-logger) .

I changed between all these logging libraries both for speed and to get rid of strange bugs. I needed a logger that was fast on average, but more importantly had low latency in the worst case. As in you cant have a realtime application, that once in a while blocks on logging for many seconds. Much better to drop messages when logging queue is full. I'm happy the way nanolog does it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants