You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2015/10/18 18:18:05 UTC

[jira] [Resolved] (LOG4J2-764) Migrate PerformanceComparison to log4j-perf

     [ https://issues.apache.org/jira/browse/LOG4J2-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma resolved LOG4J2-764.
--------------------------------
    Resolution: Won't Fix

I think Ralph likes keeping the PerformanceComparison JUnit test as a quick and dirty way to eyeball the current performance. It only takes about 10 seconds, I don't mind keeping it there.

> Migrate PerformanceComparison to log4j-perf
> -------------------------------------------
>
>                 Key: LOG4J2-764
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-764
>             Project: Log4j 2
>          Issue Type: Sub-task
>          Components: Core
>    Affects Versions: 2.0.1
>            Reporter: Matt Sicker
>            Priority: Minor
>
> This benchmark test is rather similar to the debug-disabled one. However, this test uses a different set of configuration files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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