简体   繁体   English

Hyperledger Fabric性能-每个通道多个订购者vs一个订购者

[英]Hyperledger Fabric Performance - Multiple Orderers vs Single Orderer Per Channel

In Fabric there are two ordering types: Solo and Kafka. 在Fabric中,有两种订购类型:Solo和Kafka。 When using Kafka, it is possible to have multiple orderers per channel. 使用Kafka时,每个频道可能有多个订购者。

In addition to fault tolerance, would having more than one orderer per channel have speed improvements? 除了容错能力之外,每个通道有一个以上的订购器是否还会提高速度? My understanding is solo would actually be faster because it requires less overhead? 我的理解是独奏实际上会更快,因为它需要更少的开销?

The official docs is pretty light on discussing performance implications regarding this topic. 官方文档非常适合讨论有关此主题的性能问题。

I would recommend using Kafka, just to avoid the single point of failure you get when using Solo. 我建议使用Kafka,以避免使用Solo时出现单点故障。

In addition to that, the ordering service is unlikely to be a performance bottleneck, as mentioned in the Hyperledger Fabric paper (Section 5.2). 除此之外,如Hyperledger Fabric论文所述 (第5.2节),订购服务不太可能成为性能瓶颈。 You're more likely going to be limited by computationally intensive signature verification in the validation phase or network bandwidth. 在验证阶段或网络带宽中,您很可能会受到计算量大的签名验证的限制。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 每个通道(主题)使用一个分区是否会阻止Hyperledger Fabric水平扩展订购程序? - Does using a single partition per channel (topic) stop Hyperledger Fabric from scaling orderers horizontally? Hyperledger Fabric应用程序中的订购者断开连接 - Orderer disconnections in a Hyperledger Fabric application 卡夫卡恐慌Hyperledger织物订购者 - Kafka panics Hyperledger fabric orderer Hyperledger Fabric定购者将无法从其他计算机连接到Kafka Brokers - Hyperledger fabric Orderers will not connect to Kafka Brokers from a different machine Kafka通过Hyperledger Fabric Orderer连接给出无效的接收大小 - Kafka gives Invalid receive size with Hyperledger Fabric Orderer connection Hyperledger Fabric-通道尚未启动 - Hyperledger Fabric - Channel hasn't started yet 在(hyperledger fabric)kafka订购服务中,哪个订购者节点将对块进行签名并将其广播给所有锚点对等点 - In (hyperledger fabric)kafka ordering service which orderer node will be signing and broadcasting the block to all the anchor peers 无法在Hyperledger Fabric网络中设置Kaka订购者:意外的主题级元数据错误:kafka服务器:复制因子无效 - Unable to setup Kaka Orderers in Hyperledger Fabric network:Unexpected topic-level metadata error: kafka server: Replication-factor is invalid 在超级账本结构上使用 kafka 订购服务创建通道的奇怪行为 - Wierd behavior on channel creation with kafka ordering service on hyperledger fabric Apache Kafka多生产者vs单生产者表现 - apache kafka multiple producer vs single producer performance
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM