+1 to choose the Parallel Collector temporarily as Uwe suggests so we can see distinct effects of the separate changes.
I suppose the benchmarks should continue to prefer the default JVM settings, as it is how users will consume Lucene. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Thu, Apr 25, 2019 at 6:03 PM Uwe Schindler <u...@thetaphi.de> wrote: > Maybe do this temporary, to not have 2 changes at the same time. > > Uwe > > Am April 25, 2019 9:48:35 PM UTC schrieb Michael McCandless < > luc...@mikemccandless.com>: >> >> Yeah I'm just using the JDK's default in the nightly benchmarks. >> >> Should I override back to the parallel collector? >> >> Mike McCandless >> >> http://blog.mikemccandless.com >> >> >> On Thu, Apr 25, 2019 at 5:44 PM Uwe Schindler <u...@thetaphi.de> wrote: >> >>> Hi, >>> >>> I am not sure how Mike's benchmarks are setup and if he chooses a >>> specific garbage collector. >>> >>> Java 8 defaults to ParallelGC, Java 11 defaults to G1, which may slow >>> down up to 10% as it is not optimized for throughput. >>> >>> So to compare you gave to be specific in your GC choices. >>> >>> Uwe >>> >>> Am April 25, 2019 5:57:16 PM UTC schrieb Nicholas Knize < >>> nkn...@gmail.com>: >>>> >>>> Earlier this week I noticed a significant across the board performance >>>> regression on the nightly geo benchmarks >>>> <https://home.apache.org/~mikemccand/geobench.html>. It appears this >>>> regression can also be seen on other lucene benchmarks >>>> <https://home.apache.org/~mikemccand/lucenebench/SloppyPhrase.html> and >>>> appears to correspond to the upgrade to JDK 11. >>>> >>>> Any thoughts? >>>> >>>> Nicholas Knize, Ph.D., GISP >>>> Geospatial Software Guy | Elasticsearch >>>> Apache Lucene PMC Member and Committer >>>> nkn...@apache.org >>>> >>> >>> -- >>> Uwe Schindler >>> Achterdiek 19, 28357 Bremen >>> https://www.thetaphi.de >>> >> > -- > Uwe Schindler > Achterdiek 19, 28357 Bremen > https://www.thetaphi.de >
