If the users only should have access to search their own documents, it would probably make sense to keep their respective index locally. Besides greater query speed, it would also simplify things when updating/appending the index. So, that would mean one index, one IndexModifier and one IndexSearcher living on each persons computer. Or am I missing something?
Fredrik On 5/26/06, acorcutt <[EMAIL PROTECTED]> wrote:
Hello, I'm just starting out with lucene and need to decide how to organize my index's.. I have a project where many users (1000's) will need to search only there own documents, maybe upto 1000 documents each at a time I'm trying to decide if I should go with 1 large index or one smaller index for each user, I would guess that 1 smaller index per user would give faster search results, but is it a good idea with regards to using many index reader/writers at once performance/memory wise? - with the 1 big index approach I can just keep 1 of each open globaly. Also is there big performance loss opening/closing readers as a user needs them? I guess my options are really just: 1. One large index / One global reader/writer. 2. Many index's / many global readers/writers. 3. Many index's / open&close index's as needed any advice appreciated, thanks Anthony -- View this message in context: http://www.nabble.com/Should+I+use+one+or+many+index%27s--t1684400.html#a4568925 Sent from the Lucene - General forum at Nabble.com.
