[ https://issues.apache.org/jira/browse/SUREFIRE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391019#comment-16391019 ]
David Georg Reichelt commented on SUREFIRE-1454: ------------------------------------------------ I did not believe that this patch also solves the issue and therefore created a benchmark: [https://github.com/DaGeRe/surefire-benchmark] . It indicates that surefire 3 ( [https://github.com/DaGeRe/surefire-benchmark/blob/master/results/surefire3.png] ) is performing similiar as my original patch ( [https://github.com/DaGeRe/surefire-benchmark/blob/master/results/surefire_dagerepatch.png] ), while the old surefire version is very slow ( [https://github.com/DaGeRe/surefire-benchmark/blob/master/results/surefire219.png] ). Therefore, it seems like everythings is fine. > Speedup Standard Output if Tests > -------------------------------- > > Key: SUREFIRE-1454 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1454 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin, process > forking > Reporter: Tibor Digana > Assignee: Tibor Digana > Priority: Major > Fix For: 2.21.0 > > > Currently, surefire creates a new byte array with size of the input *3 for > saving the unescaped input. This made surefire way slower than running a test > directly in eclipse or with gradle, if it used standardout or error heavily. > By using a list for saving the elements and converting them to an array > afterwards, this problem is solved, and stdout-heavy surefire tests get > faster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
