You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/25 22:02:04 UTC

[jira] [Commented] (SOLR-10415) Within solr-core, debug/trace level logging should use parameterized log messages

    [ https://issues.apache.org/jira/browse/SOLR-10415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025457#comment-16025457 ] 

ASF GitHub Bot commented on SOLR-10415:
---------------------------------------

Github user tflobbe commented on the issue:

    https://github.com/apache/lucene-solr/pull/182
  
    This PR can be closed, right?


> Within solr-core, debug/trace level logging should use parameterized log messages
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-10415
>                 URL: https://issues.apache.org/jira/browse/SOLR-10415
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Michael Braun
>            Priority: Trivial
>
> Noticed in several samplings of an active Solr that several debug statements were taking decently measurable time because of the time of the .toString even when the log.debug() statement would not output because it was effectively INFO or higher. Using parameterized logging statements, ie 'log.debug("Blah {}", o)' will avoid incurring that cost.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org