NightOwl888 commented on issue #333: URL: https://github.com/apache/lucenenet/issues/333#issuecomment-685451453
Without seeing your test, there is not a lot I can tell you. You didn't even mention what versions of Lucene/Lucene.NET you are testing. Of course, the only apples to apples way to test this would be either to run: - Lucene.NET 3.0.3 against its closest counterpart in Lucene, 3.0.1 - Lucene.NET 4.8.0 against Lucene 4.8.0 Since Lucene 4.8.0 was designed to run with Java 6, you would also need to get a copy of a Java 6 runtime to run it on. And since Java 6 is not available for download from any official source anymore, I strongly suspect you are not doing either of these exact version tests on the version of Java it was designed to run on. Do note that we have recently [set up benchmarks](https://github.com/apache/lucenenet/pull/310) across each of the betas, and we have approximately doubled search performance since 4.8.0-beta00007, so if you are testing on an older beta you will definitely see performance degradation. Of course, it is possible you have stumbled upon a severe bottleneck in a specific Analyzer, Tokenizer, Codec, Query, or other component, but again, without seeing the code there isn't much we can do. Could you post this POC somewhere in a form where it can be *run* in both Java and .NET without too much extra configuration, and some setup instructions to get it up and running? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
