[LOG4J2-761] Move performance tests from JUnit to log4j-perf

• Type: Test
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0.1
• Component/s: Core
• Labels: benchmark test
• Assignee: Unassigned
• Reporter: Matt Sicker
• Created: 03/Aug/14 22:35
• Updated: 27/Apr/16 15:51

Description

Firstly, all the JUnit tests marked with the category:

@Category(PerformanceTests.class)

should all be ported over to the log4j-perf module. The tests marked with this category generally only output performance benchmark data and don't perform any actual unit testing of their own. Now that we have several examples of how to use JMH, it would be a good idea to clean up our unit tests as such. This way, we don't have to waste time in the build performing benchmark tests that aren't even verified in any way.

Sub-Tasks

• Migrate DebugDisabledPerformanceComparison to log4j-perf: Closed
• Migrate PerformanceComparison to log4j-perf: Closed
• Migrate PerformanceRun to log4j-perf: Open
• Migrate FilterPerformanceComparison to log4j-perf: Open
• Migrate JdbcH2AppenderTest#testPerformanceOfAppenderWith1000Events() to log4j-perf: Closed
• Migrate JdbcHyperSqlAppenderTest#testPerformanceOfAppenderWith1000Events() to log4j-perf: Closed
• Migrate JpaH2AppenderTest#testPerformanceOfAppenderWith10000EventsUsingBasicEntity to log4j-perf: Closed
• Migrate JpaHyperSqlAppenderTest#testPerformanceOfAppenderWith10000EventsUsingBasicEntity to log4j-perf: Closed