rmuir commented on issue #15212:
URL: https://github.com/apache/lucene/issues/15212#issuecomment-3321595845
> You could get a more realistic estimate of individual tests if you run
with a single test jvm (and one gradle worker)
Or if you have a wimpy machine with only two cores. Here's what I see:
```
The slowest tests during this run:
50.07s TestPriorityQueue.testRemovalsAndInsertions (:lucene:core)
48.86s TestRescoreTopNQuery.testRescoreField (:lucene:core)
34.77s TestIndexOrDocValuesQuery.testUseIndexForSelectiveMultiValueQueries
(:lucene:core)
31.48s TestHnswFloatVectorGraph.testRamUsageEstimate (:lucene:core)
23.41s TestHnswByteVectorGraph.testRamUsageEstimate (:lucene:core)
21.42s TestBPReorderingMergePolicy.testReorderOnAddIndexes (:lucene:misc)
20.90s TestBPReorderingMergePolicy.testReorderOnMerge (:lucene:misc)
18.20s TestTermInSetQuery.testDuel (:lucene:core)
17.16s TestIDVersionPostingsFormat.testGlobalVersions (:lucene:sandbox)
16.72s TestAddTaxonomy.testBig (:lucene:facet)
```
I also know from doing this in the past, that some tests fluctuate a lot
because maybe they have a `numThreadsOrIters = random(10, 1000000)`-type of
logic. You can run whole test suite again and find new slow ones...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
