estions-Required-110-Concurrency-users-indexing-on-Lucene-dont-finish-in-200-ms-tp4116625p4119186.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apach
; View this message in context:
> http://lucene.472066.n3.nabble.com/Suggestions-Required-110-Concurrency-users-indexing-on-Lucene-dont-finish-in-200-ms-tp4116625p4118730.html
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
>
>
A correction on the system details posted earlier...
Windows runs on : 1CPU, 1 cores. 8 GB RAM
Linux runs on : 1 CPU , 2 cores, 8 GB RAM
--
View this message in context:
http://lucene.472066.n3.nabble.com/Suggestions-Required-110-Concurrency-users-indexing-on-Lucene-dont-finish-in-200-ms
, 4 cores. 8 GB RAM
Linux runs on : 1 CPU , 2 cores, 8 GB RAM
-Vidhya
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Thursday, February 20, 2014 6:03 PM
To: Lucene Users
Subject: Re: [Suggestions Required] 110 Concurrency users indexing on
; 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/Sugge
)
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-
View this message in context:
> http://lucene.472066.n3.nabble.com/Suggestions-Required-110-Concurrency-users-indexing-on-Lucene-dont-finish-in-200-ms-tp4116625p4117133.html
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
>
> -
3.nabble.com/Suggestions-Required-110-Concurrency-users-indexing-on-Lucene-dont-finish-in-200-ms-tp4116625p4117133.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: java-u
Lucene's indexing is very concurrent, especially in 4.x where we've
added concurrent flushing:
http://blog.mikemccandless.com/2011/05/265-indexing-speedup-with-lucenes.html
Are you sure the bottleneck is in Lucene and not e.g. the server-side
handling of suddenly receiving 110 X 10,50,100 document
Group -
We have an Indexing and Searching Service (using Lucene 4.0) implemented over
REST as part of our framework, which all the related modules will use to
publish data that make it available for the UI.
Moreover, every rest call that our service receives has a proxy timeout limit
of 20
10 matches
Mail list logo