[
https://issues.apache.org/jira/browse/JENA-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222201#comment-16222201
]
ASF GitHub Bot commented on JENA-1407:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/297
From the documentation, the default mode of Surefire is that
`<threadCount>` is count-per-core.
{noformat}
perCoreThreadCount (Default: true)
(JUnit 4.7 provider) Indicates that threadCount, threadCountSuites,
threadCountClasses, threadCountMethods are per cpu core.
User property: perCoreThreadCount
{noformat}
So setting thread count to 50% CPUs is a number per core?
Let's go with the original PR for the 3.5.0 RC2.
> Improvements to build/test time of Elephas tests.
> -------------------------------------------------
>
> Key: JENA-1407
> URL: https://issues.apache.org/jira/browse/JENA-1407
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Priority: Minor
> Attachments: Elephas-Test-Times
>
>
> The Elephas test can take a significant proportion of the total build time.
> if this could be improved without lost of testing, development and release
> work, building locally would be improved.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
