[
https://issues.apache.org/jira/browse/SOLR-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Robert Miller updated SOLR-15477:
--------------------------------------
Parent: SOLR-15509
Issue Type: Sub-task (was: Improvement)
> Logging Performance
> -------------------
>
> Key: SOLR-15477
> URL: https://issues.apache.org/jira/browse/SOLR-15477
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Robert Miller
> Priority: Major
>
> Once you remove almost all performance issues and unnecessary garbage
> generation, logging starts to sit at the top of method and gc perf profiling
> (well, xml config still competes on gc - you can improve that 90% and it's
> still fights to be king of the hill) during test runs. This is the case even
> with fairly reduced logging and configuration optimizations.
> At that point, exception logging is the big killer (no garbage free option),
> so in a mostly clean running system this will likely be less the case.
> There are a variety of configuration options that can boost the logging
> impact. Fairly critical to it all is telling log4j2 that no, Solr is not a
> webapp, please dont punish.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
