summaryrefslogtreecommitdiff
path: root/t/t4018/python-class
diff options
context:
space:
mode:
authorLibravatar Emily Shaffer <emilyshaffer@google.com>2020-05-12 14:44:20 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-05-12 15:30:39 -0700
commit98a136474082cdc7228d7e0e45672c5274fab701 (patch)
tree008d37ad3da3f53594d21a992a92ad1bda10aa98 /t/t4018/python-class
parentThe eighth batch (diff)
downloadtgif-98a136474082cdc7228d7e0e45672c5274fab701.tar.xz
trace2: log progress time and throughput
Rather than teaching only one operation, like 'git fetch', how to write down throughput to traces, we can learn about a wide range of user operations that may seem slow by adding tooling to the progress library itself. Operations which display progress are likely to be slow-running and the kind of thing we want to monitor for performance anyways. By showing object counts and data transfer size, we should be able to make some derived measurements to ensure operations are scaling the way we expect. Signed-off-by: Emily Shaffer <emilyshaffer@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4018/python-class')
0 files changed, 0 insertions, 0 deletions