[ https://issues.apache.org/jira/browse/SOLR-12642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588288#comment-16588288 ]
Shalin Shekhar Mangar commented on SOLR-12642: ---------------------------------------------- [~elyograg], the question is not whether http2 is as fast or faster. The question is how much extra cost is it to process updates independently vs processing them in a batch. There are per-request buffers and computations done by Solr e.g. from parsing headers to deciding which core to route the request to 8KB buffer used by FastInputStream etc. > SolrCmdDistributor should send updates in batch when use Http2SolrClient? > ------------------------------------------------------------------------- > > Key: SOLR-12642 > URL: https://issues.apache.org/jira/browse/SOLR-12642 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Cao Manh Dat > Priority: Major > > In the past, batch updates are sent in a single stream from the leader, the > replica will create a single thread to parse all the updates. For the > simplicity of {{SOLR-12605}}, the leader is now sending individual updates to > replicas, therefore they are now parsing updates in different threads which > increase the usage of memory and CPU. > In the past, this is an unacceptable approach, because, for every update, we > must create different connections to replicas. But with the support of > HTTP/2, all updates will be sent in a single connection from leader to a > replica. Therefore the cost is not as high as it used to be. > On the other hand, sending individual updates will improve the indexing > performance and better error-handling for failures of a single update in a > batch. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org