You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using segment replication, TransportShardBulkAction.performOpOnReplica() is invoked on replicas in order to persist the document into the translog on the replica and give the same durability guarantees as document replication. Here are two snapshots of CPU profiling for the same workload for both docrep and segrep:
Document Replication
Segment Replication
It clearly shows that NRTReplicationEngine does not invoke IndexWriter, whereas InternalEngine does. This is expected since the replicas do not need to index the document. However, a lot of work is spent doing DocumentMapper#parse in both cases. The question is: can this be refactored so that with segment replication the replicas avoid doing some or all of that document parsing?
The text was updated successfully, but these errors were encountered:
When using segment replication, TransportShardBulkAction.performOpOnReplica() is invoked on replicas in order to persist the document into the translog on the replica and give the same durability guarantees as document replication. Here are two snapshots of CPU profiling for the same workload for both docrep and segrep:
Document Replication
Segment Replication
It clearly shows that NRTReplicationEngine does not invoke
IndexWriter
, whereas InternalEngine does. This is expected since the replicas do not need to index the document. However, a lot of work is spent doingDocumentMapper#parse
in both cases. The question is: can this be refactored so that with segment replication the replicas avoid doing some or all of that document parsing?The text was updated successfully, but these errors were encountered: