You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/02/28 15:03:00 UTC
[jira] [Work logged] (LOG4J2-3558) Make the default thread priority configurable
[ https://issues.apache.org/jira/browse/LOG4J2-3558?focusedWorklogId=848094&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848094 ]
ASF GitHub Bot logged work on LOG4J2-3558:
------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Feb/23 15:02
Start Date: 28/Feb/23 15:02
Worklog Time Spent: 10m
Work Description: vy closed pull request #973: LOG4J2-3558: make default priority configurable
URL: https://github.com/apache/logging-log4j2/pull/973
Issue Time Tracking
-------------------
Worklog Id: (was: 848094)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)