: [Hyperledger Fabric] HLF thoughput


Mark Rakhmilevich
 

Satya,
In our experience, transaction throughput is significantly affected by payload size as well as ordering service settings. You might want to try to configure the ordering service with more transactions per block and longer block cutting times to see if that helps. We have seen this increase the overall throughput at the cost of additional latency. Your network throughput might also be a factor, particularly if your peer nodes are not running at very high CPU utilization.

Thanks,
Mark

-----Original Message-----
From: fabric@... <fabric@...> On Behalf Of Satya
Sent: Friday, August 19, 2022 6:16 PM
To: fabric@...
Subject: [External] : [Hyperledger Fabric] HLF thoughput

Hi,

We observed that for max 200 Txs only responses have been received at client node in a 3 organization setup each having 2 endorsing peers and with 3 orderer nodes over 1 channel. All responses have been received with in a time limit of 1sec. Each node (peer or orderer) has 8GB RAM and 1 CPU Core and are running in separate VMs. Our Tx size is roughly 10kb and the similar behavior observed up to 45kb. How can this tps rate of 200 be improved further, any suggestions. We are using HLF 2.2.3.

Satya
------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://urldefense.com/v3/__https://www.facebook.com/CDACINDIA__;!!ACWV5N9M2RV99hQ!L-ul8VCflABv-siD2lX2cvzPyonLb0_PHw5HxPynzaEU_Z_ONinmObLxOAGuEU_h4tTdz5TTwCyaTGtex-vy94l7$ & Twitter: @cdacindia ]

This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken.
------------------------------------------------------------------------------------------------------------


Peter
 

Dear Friend´╝î

Thanks for your kindly reply, and thanks for the detailed date you offered. The TPS from different permissioned blockchains are quite distinguished under different test conditions. Thanks again!

Best Regards,
Peter




At 2022-08-20 09:28:21, "Mark Rakhmilevich" <mark.rakhmilevich@...> wrote: >Satya, > In our experience, transaction throughput is significantly affected by payload size as well as ordering service settings. You might want to try to configure the ordering service with more transactions per block and longer block cutting times to see if that helps. We have seen this increase the overall throughput at the cost of additional latency. Your network throughput might also be a factor, particularly if your peer nodes are not running at very high CPU utilization. > >Thanks, > Mark > > > >-----Original Message----- >From: fabric@... <fabric@...> On Behalf Of Satya >Sent: Friday, August 19, 2022 6:16 PM >To: fabric@... >Subject: [External] : [Hyperledger Fabric] HLF thoughput > >Hi, > >We observed that for max 200 Txs only responses have been received at client node in a 3 organization setup each having 2 endorsing peers and with 3 orderer nodes over 1 channel. All responses have been received with in a time limit of 1sec. Each node (peer or orderer) has 8GB RAM and 1 CPU Core and are running in separate VMs. Our Tx size is roughly 10kb and the similar behavior observed up to 45kb. How can this tps rate of 200 be improved further, any suggestions. We are using HLF 2.2.3. > >Satya >------------------------------------------------------------------------------------------------------------ >[ C-DAC is on Social-Media too. Kindly follow us at: >Facebook: https://urldefense.com/v3/__https://www.facebook.com/CDACINDIA__;!!ACWV5N9M2RV99hQ!L-ul8VCflABv-siD2lX2cvzPyonLb0_PHw5HxPynzaEU_Z_ONinmObLxOAGuEU_h4tTdz5TTwCyaTGtex-vy94l7$ & Twitter: @cdacindia ] > >This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. >------------------------------------------------------------------------------------------------------------ > > > > > > > > > > >