Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: throughput faq #1656

Merged
merged 3 commits into from
Nov 22, 2024
+1 −1
Merged

fix: throughput faq #1656

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e0e6a55
change for throughput faq
psankhe28 Nov 16, 2024
dc4e496
changed faq
psankhe28 Nov 22, 2024
c6ba5b1
changes
psankhe28 Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/source/getting-started/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ There is another configuration file, namely `./config/default.yaml`, containing
## **IV. Other Questions Related to Caliper**

**Q:** How can I calculate the throughput (TPS)?
**A:** Caliper will record the submitting time and committing time (the time when the Tx is committed on the ledger or when the failure occurred) for each Tx. So the send rate is calculated by `(Succ+Fail) / (last submitting time - first submitting time)`. The throughput is calculated by `Succ/(last committing time - first submitting time)`, here only successful committed Txs will be calculated.
**A:** Caliper will record the submitting time and committing time (the time when the Tx is committed on the ledger or when the failure occurred) for each Tx. So the send rate and the throughput are calculated by `(Succ+Fail) / (last submitting time - first submitting time)`. This means both successful and failed transactions are included in the throughput and send rate calculations.

## V. **Other Questions Related to the Backend Blockchain System**

Expand Down
Loading