From 4f73fb4f7c9dee0ca051a4aca50d10f7257353bc Mon Sep 17 00:00:00 2001 From: Kjell Hedstrom Date: Mon, 6 Jul 2015 22:25:45 -0600 Subject: [PATCH 1/3] Update README.markdown --- README.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.markdown b/README.markdown index a016488..62c467b 100644 --- a/README.markdown +++ b/README.markdown @@ -193,9 +193,9 @@ If you like this logger (or not) it would be nice with some feedback. That way I 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 +or at ```Hedstrom at KjellKod dot cc``` Cheers -Kjell *(a.k.a. KjellKod)* \ No newline at end of file +Kjell *(a.k.a. KjellKod)* From 389a7d695cc65c1fe27fff9178e119ee03869fcf Mon Sep 17 00:00:00 2001 From: Kjell Hedstrom Date: Mon, 6 Jul 2015 22:32:05 -0600 Subject: [PATCH 2/3] Update README.markdown --- README.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.markdown b/README.markdown index 62c467b..54be1f2 100644 --- a/README.markdown +++ b/README.markdown @@ -186,7 +186,11 @@ 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. 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 very 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. From 07c74bbbc33574ae3563a39a80a3a79cb84fdb34 Mon Sep 17 00:00:00 2001 From: Kjell Hedstrom Date: Mon, 6 Jul 2015 22:34:20 -0600 Subject: [PATCH 3/3] Update README.markdown --- README.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.markdown b/README.markdown index 54be1f2..eb365fa 100644 --- a/README.markdown +++ b/README.markdown @@ -187,9 +187,9 @@ make ``` #Performance -G3log aims to keep all background logging to sinks with as little log overhead as possible to the logging sink. 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. +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 very 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. +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