Thanks for the positive feedback. :-) Yes, right now the benchmark only uses one IndexSearcher for all threads, but I have completed an extension that allows you to either 1) have multiple searchers for the same index; or 2) have multiple indexes (copies of one another) with a single searcher per copy (to test when you have your index copies on separate disks, SANS, NAS, etc).
I will rerun my benchmarks with increasing numbers of readers & post the results in the next couple of days. -glen 2008/6/10 Chris Lu <[EMAIL PROTECTED]>: > Good work! > I would like to see how it performs with several index reader instances, > which is said to increase concurrency. > > -- > Chris Lu > ------------------------- > Instant Scalable Full-Text Search On Any Database/Application > site: http://www.dbsight.net > demo: http://search.dbsight.com > Lucene Database Search in 3 minutes: > http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes > DBSight customer, a shopping comparison site, (anonymous per request) got > 2.6 Million Euro funding! > > On Mon, Jun 9, 2008 at 3:51 PM, Glen Newton <[EMAIL PROTECTED]> wrote: > >> A number of people have asked about query benchmarks. >> >> I have posted benchmarks for concurrent query requests for Lucene >> 2.3.1 on my blog, where I look at 1 - 4096 concurrent requests: >> >> http://zzzoot.blogspot.com/2008/06/simultaneous-threaded-query-lucene.html >> >> I hope you find this useful. >> >> thanks, >> >> Glen >> >> -- >> >> - >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
