Is there any debug settings to see where the time is taken during a distributed search?
I suspect some of the time is spent in network overhead between the shards consolidating the results but I don't have a good way to pin this down. Sometimes, the results come back very quickly - so I know it is not all network related and want to know if there is a way to see this from within a distributed request. Turning on... debugQuery=on does not seem to report distributed performance statistics. When I query all shards together, I get: http://host:8880/solr/select/?shards=host1:8881/solr,host2:8882/solr,host3:8883/solr,host4:8884/solr,host5:8885/solr,host6:8886/solr,host7:8887/solr&q=cancer 428 then 287 If I isolate each shard like this: http://host:8880/solr/select/?shards=host1:8881/solr&q=cancer 195,146,844,230,51,48,43 Then going directly gets this: http://host1:8881/solr/select/?q=cancer 0,1,0,1,1,1,1 I can see taking a few sample responses is not conclusive to say one shard is slower or faster. However, the query time directly is orders of magnitude faster than through shards. My only guess is this is network based and involved in passing the results around in order to reduce them. Is there any debug or way to confirm and investigate this further? -- Regards, Ian Connor
