[jira] [Work logged] (LOG4J2-3558) Make the default thread priority configurable

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-3558?focusedWorklogId=848190&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848190 ]

ASF GitHub Bot logged work on LOG4J2-3558:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Mar/23 06:55
            Start Date: 01/Mar/23 06:55
    Worklog Time Spent: 10m 
      Work Description: ppkarwasz commented on PR #973:
URL: https://github.com/apache/logging-log4j2/pull/973#issuecomment-1449446582

   This was closed automatically by Github because we renamed the `release-2.x` branch to `2.x`. Feel free to resubmit to the `2.x` branch.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 848190)
    Time Spent: 20m  (was: 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: 20m
>  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)