[英]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.