You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Marvin Wu (Jira)" <ji...@apache.org> on 2022/07/22 15:43:00 UTC
[jira] [Commented] (LOG4J2-3558) Make the default thread priority configurable
[ https://issues.apache.org/jira/browse/LOG4J2-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570091#comment-17570091 ]
Marvin Wu commented on LOG4J2-3558:
-----------------------------------
I raised PR 973 for this: https://github.com/apache/logging-log4j2/pull/973
> Make the default thread priority configurable
> ---------------------------------------------
>
> Key: LOG4J2-3558
> URL: https://issues.apache.org/jira/browse/LOG4J2-3558
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.18.0
> Reporter: Marvin Wu
> Priority: Major
>
> The story behind would be some incapability in performance tuning.
> During the tuning, it's found that the threads running business logic are competing resources with other supporting threads, e.g. async. notification senders, stats aggregators and loggers.
> With the default thread priority configurable, it's now possible to --
> # Check if and how it contributes to the performance of business logic when loggers run in lower priority
> # Check if some side effects when loggers run in lower priority
--
This message was sent by Atlassian Jira
(v8.20.10#820010)