CODEWITHSUNDEEP
hyperledger-fabricblockchainhyperledger
Yash Shukla
Yash Shukla

Reputation: 121

Transactions per second vs Time for one transaction in Hyperledger

The Hyperledger on paper states that it supports 3500 transactions per second But what is the time it takes to commit/execute one transaction? is it equal to one block time? can we use Hyperledger for a realtime application that needs a transaction to be done within 100 ms?

Upvotes: 0

Views: 1163

Answers (1)

yacovm
yacovm

Reputation: 5140

3500 transactions per second means that on average, 3500 transactions were created by some clients and then appeared in some next newly created block within one second.

It can be that several blocks were created in that second.

You can't use Fabric, or any other consensus mechanism that uses IP networks for a real time application, simply because that if the network transmission can be delayed for more than 100ms.

You can, however - make the consensus service in Fabric use low batch timeouts (say, of 10ms) and then blocks would be formed on a frequent basis and you'll have a transaction latency less than 100ms on average.

Upvotes: 1

Related Questions