Hi, Does your query really need to search all 40 shards? If not, dispatching the query only to shards that need to be queried will help.
Otis -- SOLR Performance Monitoring - http://sematext.com/spm/index.html On Tue, Mar 26, 2013 at 11:17 AM, qungg <qzheng1...@gmail.com> wrote: > Hi, > > I have 40 shards running on 48 core machine with 256GB RAM (The data is > about 40 GB). I am using legacy distributed method as setup. So I have one > additional shard with no data. Queries would go to this shard and the shard > would merge result from the rest of the 40 shards. From the log, I see that > query time for each shard is almost instant, but the controller shard take a > long time to merge the result. > > I tried to cache the results to controller shards like I do in each > individual shard, but it wouldn't not cache, probably because the controller > shard contains no documents. > > I can tell that merging result is the bottle neck here, but I couldn't find > a way to fix it. Please let me know if you guys have any suggestion. Thanks > in advance! > > Best Regards, > Qun > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Slow-performance-on-distributed-search-tp4051434.html > Sent from the Solr - User mailing list archive at Nabble.com.
