From 8c371dd2fb3d69d8fa34f20eecd0629528c82732 Mon Sep 17 00:00:00 2001 From: Justin Starry Date: Wed, 21 Aug 2019 09:59:23 -0400 Subject: [PATCH] Update performance metrics page in the book (#5581) --- book/src/performance-metrics.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/book/src/performance-metrics.md b/book/src/performance-metrics.md index fef9d2484..7727e5299 100644 --- a/book/src/performance-metrics.md +++ b/book/src/performance-metrics.md @@ -7,14 +7,16 @@ confirmed by super majority of the cluster (Confirmation Time). Each cluster node maintains various counters that are incremented on certain events. These counters are periodically uploaded to a cloud based database. Solana's metrics dashboard fetches these counters, and computes the performance metrics and displays -it on the dashboard. +it on the dashboard. ## TPS -The leader node's banking stage maintains a count of transactions that it recorded. -The dashboard displays the count averaged over 2 second period in the TPS time series -graph. The dashboard also shows per second mean, maximum and total TPS as a running -counter. +Each node's bank runtime maintains a count of transactions that it has processed. +The dashboard first calculates the median count of transactions across all metrics +enabled nodes in the cluster. The median cluster transaction count is then averaged +over a 2 second period and displayed in the TPS time series graph. The dashboard also +shows the Mean TPS, Max TPS and Total Transaction Count stats which are all calculated from +the median transaction count. ## Confirmation Time @@ -26,4 +28,4 @@ super majority vote, and when one of its children forks is frozen. The node assigns a timestamp to every new fork, and computes the time it took to confirm the fork. This time is reflected as validator confirmation time in performance metrics. The performance dashboard displays the average of each validator node's confirmation time -as a time series graph. +as a time series graph.