Adjust thread count calculation in ChronicleRollingIssueTest for improved scalability

Author: peter-lawrey

src/test/java/net/openhft/chronicle/queue/ChronicleRollingIssueTest.java

@@ -42,11 +42,8 @@ public void tearDown() {
 
     @Test(timeout = 180_000L)
     public void test() throws InterruptedException {
-        // Cap at 31 appenders. The old min(64, processors*4) - 1 formula started 63
-        // appenders on large CI agents, all queueing on the same writeLock and each holding
-        // it for mmap+EOF-probe work. This still exercises contention without scaling
-        // pathologically with core count.
-        int threads = Math.max(2, Math.min(32, Runtime.getRuntime().availableProcessors() * 2) - 1);
+        int processors = Runtime.getRuntime().availableProcessors();
+        int threads = Math.max(2, Math.min(64, processors * 2) - 1);
         int messages = 100;
 
         AtomicInteger count = new AtomicInteger();