Hi Grant, > I have serious doubts about releasing this new API until these > performance issues are resolved and better proven out from a usability > standpoint.
I think LUCENE-1796 has fixed the performance problems, which was caused by a missing reflection-cache needed for bw compatibility. I hope to commit soon! 2.9 may be a little bit slower when you mix old and new API and do not reuse Tokenizers (but Robert is already adding reusableTokenStream to all contrib analyzers). When the backwards layer is removed completely or setOnlyUseNewAPI is enabled, there is no speed impact at all. Michael: The TokenWrapper added cost was there in 2.9 before the TokenStream overhaul, too, as the TokenWrapper-like code was there implemented similarily inside DocInverter. Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
