Hi, We have results from a different test case with multiple threads (internal id GRANITE-5572). We have 50 full thread dumps, and there I count:
* 259 cases of LuceneIndex.java line 365: IndexReader reader = DirectoryReader.open(directory); * 43 cases of LuceneIndex.java line 379: TopDocs docs = searcher.search(query, Integer.MAX_VALUE); * 13 cases of LuceneInde.java line 382: String path = reader.document(doc.doc, PATH_SELECTOR).get(PATH); So, running the Lucene query and getting the paths is slow, but opening the Lucene index is even slower in this test case. Regards, Thomas On 09/04/14 13:44, "Jukka Zitting" <jukka.zitt...@gmail.com> wrote: >Hi, > >On Wed, Apr 9, 2014 at 7:24 AM, Chetan Mehrotra ><chetan.mehro...@gmail.com> wrote: >> ... the testcase only fetches the first result. > >Is that a common use case? To better simulate a normal usage scenario >I'd make the benchmark fetch up to N results (where N is configurable, >with default something like 20) and access the path and the title >property of the matching nodes. > >BR, > >Jukka Zitting
