In case you are going to use core per user take a look to this patch: http://wiki.apache.org/solr/LotsOfCores
Trey-13 wrote: > > Hi Matt, > > In most cases you are going to be better off going with the userid method > unless you have a very small number of users and a very large number of > docs/user. The userid method will likely be much easier to manage, as you > won't have to spin up a new core every time you add a new user. I would > start here and see if the performance is good enough for your requirements > before you start worrying about it not being efficient. > > That being said, I really don't have any idea what your data looks like. > How many users do you have? How many documents per user? Are any > documents > shared by multiple users? > > -Trey > > > > On Tue, Jan 26, 2010 at 7:27 PM, Matthieu Labour > <matthieu_lab...@yahoo.com>wrote: > >> Hi >> >> >> >> Shall I set up Multiple Core or Single core for the following use case: >> >> >> >> I have X number of users. >> >> >> >> When I do a search, I always know for which user I am doing a search >> >> >> >> Shall I set up X cores, 1 for each user ? Or shall I set up 1 core and >> add >> a userId field to each document? >> >> >> >> If I choose the 1 core solution then I am concerned with performance. >> Let's say I search for "NewYork" ... If lucene returns all "New York" >> matches for all users and then filters based on the userId, then this >> is going to be less efficient than if I have sharded per user and send >> the request for "New York" to the user's core >> >> >> >> Thank you for your help >> >> >> >> matt >> >> >> >> >> >> >> > > -- View this message in context: http://old.nabble.com/Multiple-Cores-Vs.-Single-Core-for-the-following-use-case-tp27332288p27335403.html Sent from the Solr - User mailing list archive at Nabble.com.
