You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "marco polo (JIRA)" <ji...@apache.org> on 2017/05/31 18:55:04 UTC
[jira] [Comment Edited] (MINIFI-326) Explore a different logger
library
[ https://issues.apache.org/jira/browse/MINIFI-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031689#comment-16031689 ]
marco polo edited comment on MINIFI-326 at 5/31/17 6:54 PM:
------------------------------------------------------------
preliminary testing shows great promise for nanolog so far. Some minifi specific logging structs were removed that have to be re-added, but this can be done in the scope of MINIFI-326.
was (Author: phrocker):
preliminary testing shows great promise for nanolog so far.
> Explore a different logger library
> ----------------------------------
>
> Key: MINIFI-326
> URL: https://issues.apache.org/jira/browse/MINIFI-326
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Reporter: marco polo
> Priority: Minor
> Fix For: cpp-0.3.0
>
>
> When testing a PR I replaced spdlog with https://github.com/Iyengar111/NanoLog and g3log. The latter had consistent performance whereas spdlog had large variance. NanoLog seemed faster with my test case, but has other trade offs. We should explore dropping in a different logger since I've seen logging be 1-2% of cpu cycles, which is excessive for my test cases.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)