We tried a standalone program to index 50 documents from 100 threads concurrently. We executed the program for 1000 threads with 10 mins delay to avoid jvm warming issue as you suggested in last post. Also we are running with restricted heap size i.e 124MB ( as our product is running in linux with a shared heapsize of 124MB for lucene.) in both windows and linux. We can see that there is a performance difference in Windows and in linux.
Please find attached result, where we have an average time taken per thread except the first run (since it may have the jvm warming impact) Lucene_win_linux_Diff.xlsx <http://lucene.472066.n3.nabble.com/file/n4118525/Lucene_win_linux_Diff.xlsx> Please share your thought... thanks Sreedeep -- View this message in context: http://lucene.472066.n3.nabble.com/Suggestions-Required-110-Concurrency-users-indexing-on-Lucene-dont-finish-in-200-ms-tp4116625p4118525.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
