Re: Performance vs. maxBufferedAddsPerServer=10

2013-07-29 Thread Mark Miller
Yes, the internal document forwarding path is different and does not use the CloudSolrServer. It currently works with a buffer of 10. - Mark On Jul 29, 2013, at 3:10 PM, Erick Erickson wrote: > Why wouldn't it? Or are you saying that the routing to replicas > from the leader also 10/packet? Hm

Re: Performance vs. maxBufferedAddsPerServer=10

2013-07-29 Thread Erick Erickson
Why wouldn't it? Or are you saying that the routing to replicas from the leader also 10/packet? Hmmm, hadn't thought of that... On Mon, Jul 29, 2013 at 7:58 AM, Mark Miller wrote: > SOLR-4816 won't address this - it will just speed up *different* parts. There > are other things that will need to

Re: Performance vs. maxBufferedAddsPerServer=10

2013-07-29 Thread Mark Miller
SOLR-4816 won't address this - it will just speed up *different* parts. There are other things that will need to be done to speed up that part. - Mark On Jul 26, 2013, at 3:53 PM, Erick Erickson wrote: > This is current a hard-coded limit from what I've understood. From what > I remember, Mark

Re: Performance vs. maxBufferedAddsPerServer=10

2013-07-26 Thread Erick Erickson
This is current a hard-coded limit from what I've understood. From what I remember, Mark said Yonik said that there are reasons to make the packets that size. But whether this is empirically a Good Thing I don't know. SOLR-4816 will address this a different way by making SolrJ batch up the docs an