You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Christine Poerschke (JIRA)" <ji...@apache.org> on 2018/07/17 18:56:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Christine Poerschke updated SOLR-10415:
---------------------------------------
    Component/s: logging

> 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) 
>          Components: logging
>            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
(v7.6.3#76005)

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