comparison tests/test-contrib-perf.t @ 44996:c2df0bca0dfa

perf: make `hg perfwrite` more flexible The more flexible command was used recently while finding a solution for a buffering bug (eventually fixed in f9734b2d59cc (the changeset description uses a different benchmark)). In comparison to the previous version, the new version is much more flexible. While using it, the focus was on testing small writes. For this reason, by default it calls ui.write() 100 times with a single byte plus one newline byte, for 100 lines. To get the previous behavior, run `hg perfwrite --nlines=100000 --nitems=1 --item='Testing write performance' --batch-line`.
author Manuel Jacob <me@manueljacob.de>
date Fri, 05 Jun 2020 01:54:13 +0200
parents bfc68404cccd
children b8d8fd2fe75f
comparison
equal deleted inserted replaced
44995:2c920c4dbb31 44996:c2df0bca0dfa
178 test the rendering time of a given template 178 test the rendering time of a given template
179 perfunidiff benchmark a unified diff between revisions 179 perfunidiff benchmark a unified diff between revisions
180 perfvolatilesets 180 perfvolatilesets
181 benchmark the computation of various volatile set 181 benchmark the computation of various volatile set
182 perfwalk (no help text available) 182 perfwalk (no help text available)
183 perfwrite microbenchmark ui.write 183 perfwrite microbenchmark ui.write (and others)
184 184
185 (use 'hg help -v perf' to show built-in aliases and global options) 185 (use 'hg help -v perf' to show built-in aliases and global options)
186 $ hg perfaddremove 186 $ hg perfaddremove
187 $ hg perfancestors 187 $ hg perfancestors
188 $ hg perfancestorset 2 188 $ hg perfancestorset 2