aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2018-08-08 13:39:29 -0400
committerKevin O'Connor <kevin@koconnor.net>2018-08-08 13:39:29 -0400
commitcbf019a468469b6a7383cf7d079f1774ac815d6c (patch)
tree2025e7283d1006b5c513e99121a814a2affb509a
parentfbec3ebb639e6cf41d27a92c16f4afd490b493ee (diff)
downloadkutter-cbf019a468469b6a7383cf7d079f1774ac815d6c.tar.gz
kutter-cbf019a468469b6a7383cf7d079f1774ac815d6c.tar.xz
kutter-cbf019a468469b6a7383cf7d079f1774ac815d6c.zip
docs: It's difficult to estimate real-world usage from the benchmarks
Remove the prediction on real-world usage as it's not really practical to make a prediction. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
-rw-r--r--docs/Debugging.md4
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/Debugging.md b/docs/Debugging.md
index fee81f40..36a24e38 100644
--- a/docs/Debugging.md
+++ b/docs/Debugging.md
@@ -188,9 +188,7 @@ The step rate benchmark is designed to find the maximum stepping rate
that the hardware and software can reach. This benchmark stepping rate
is not achievable in day-to-day use as Klipper needs to perform other
tasks (eg, mcu/host communication, temperature reading, endstop
-checking) in any real-world usage. It is difficult to estimate actual
-real-world capacity, but as a general guide, one may approach 75% of
-these rates in practice.
+checking) in any real-world usage.
## Step rate benchmark test ##