From c994bc1d89ef8af556f60c150e55d7e585e57695 Mon Sep 17 00:00:00 2001 From: Kovid Goyal Date: Fri, 15 Jun 2018 13:51:49 +0530 Subject: [PATCH] Add more clarification about kitty's performance goals --- docs/performance.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/performance.rst b/docs/performance.rst index 297fb21a7..33def5fdf 100644 --- a/docs/performance.rst +++ b/docs/performance.rst @@ -43,3 +43,17 @@ konsole 29 - 31% As you can see, |kitty| uses much less CPU than all terminals, except xterm, but its scrolling "smoothness" is much better than that of xterm (at least to my, admittedly biased, eyes). + + +.. _perf-cat: + +.. note:: + + Some people have asked why kitty does not perform better than terminal XXX in + the test of sinking large amounts of data, such as catting a large text + file. The answer is because this is not a goal for kitty. kitty + deliberately throttles input parsing and output rendering to minimize + resource usage while still being able to sink output faster than any real + world program can produce it. Reducing CPU usage, and hence battery drain + while achieving instant response times and smooth scrolling to a human eye + is a far more important goal.