integration by parts_posterior descending artery

integration by parts_posterior descending arteryIntheclusterenvironment,eachWRITEtransactionrequiresonenetworkround-trip:theinitiatorsendstransactiondataandwaitsforresponsesfromallothernodes.Thusthedurationofatransaction

大家好,又见面了,我是你们的朋友全栈君。如果您正在找激活码,请点击查看最新教程,关注关注公众号 “全栈程序员社区” 获取激活教程,可能之前旧版本教程已经失效.最新Idea2022.1教程亲测有效,一键激活。

Jetbrains全系列IDE稳定放心使用

In the cluster environment, each WRITE transaction requires onenetwork round-trip: the initiator sends transaction data and waits forresponses from all other nodes. Thus the duration of a transaction cannot beless than the network latency (or ‘ping time’). For Ethernet the typical WRITEtransaction rate is 5-7K TPS for one thread.

 

Some common methods to increase the overall cluster performanceare:

–         Combine several small WRITE-transactions into one largetransaction so that, instead of many network round-trips, there will be onlyone.

–         Execute WRITE-transactions in several threads if possible. Thisway each thread sends and receives network packages independently, so that youcould obtain near-linear dependency of performance from the number of threads.

–         If using several write threads, it’s worth using the transactionwindow feature. Try setting the cl_params.window.length to about one half ofthe number of ‘active’ write threads. 


Note that in a cluster, all nodes can write atthe same time.  Thus, given your example of 40K TPS, two nodescould achieve 80K TPS in the aggregate, assuming no conflicts.  Note alsothat read-only transactions don’t cause any network traffic, so every nodemultiplies the number of read-only transactions that are possible.

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 举报,一经查实,本站将立刻删除。

发布者:全栈程序员-用户IM,转载请注明出处:https://javaforall.cn/181929.html原文链接:https://javaforall.cn

【正版授权,激活自己账号】: Jetbrains全家桶Ide使用,1年售后保障,每天仅需1毛

【官方授权 正版激活】: 官方授权 正版激活 支持Jetbrains家族下所有IDE 使用个人JB账号...

(0)


相关推荐

发表回复

您的电子邮箱地址不会被公开。

关注全栈程序员社区公众号