mirror of
https://github.com/KjellKod/g3log.git
synced 2024-12-14 02:57:46 +01:00
Merge pull request #19 from KjellKod/KjellKod-readme-patch
Update README.markdown
This commit is contained in:
commit
3e5da340bd
@ -186,14 +186,18 @@ cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_BUILD_TYPE=Release ..
|
||||
make
|
||||
```
|
||||
|
||||
#Performance
|
||||
G3log aims to keep all background logging to sinks with as little log overhead as possible to the logging sink and with as small "worst case latency" as possible. For this reason g3log is a good logger for many systems that deal with critical tasks. Depending on platform the average logging overhead will differ. On my laptop the average call, when doing extreme performance testing, will be about ~2 us.
|
||||
|
||||
The worst case latency is kept stabile with no extreme peaks, in spite of any sudden extreme pressure. I have a blog post regarding comparing worst case latency for g3log and other loggers which might be of interest.
|
||||
You can find it here: https://kjellkod.wordpress.com/2015/06/30/the-worlds-fastest-logger-vs-g3log/
|
||||
|
||||
#Enjoy
|
||||
If you like this logger (or not) it would be nice with some feedback. That way I can improve g3log and g2log and it is also nice to see if someone is using it.
|
||||
|
||||
If you have ANY questions or problems please do not hesitate in contacting me on my blog
|
||||
http://kjellkod.wordpress.com/2011/11/17/kjellkods-g2log-vs-googles-glog-are-asynchronous-loggers-taking-over
|
||||
or at <Hedstrom at KjellKod dot cc>
|
||||
or at ```Hedstrom at KjellKod dot cc```
|
||||
|
||||
|
||||
Cheers
|
||||
|
Loading…
Reference in New Issue
Block a user