diff options
author | Taylor Blau <me@ttaylorr.com> | 2022-10-13 01:01:55 +0300 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2022-10-13 23:35:07 +0300 |
commit | 2dcff52524e611413cb0cb49015f0d105f5f8dfa (patch) | |
tree | e36498bcc59df40715bcf4a9794cdd385e9971a2 /pack-bitmap-write.c | |
parent | 1dc4f1ef0d2528f405d71850d73d80ff1a571abd (diff) |
midx.c: instrument MIDX and bitmap generation with trace2 regions
When debugging MIDX and MIDX-bitmap related issues, it is useful to
figure out where Git is spending its time.
GitHub has been using the below trace2 regions to instrument various
components of generating a MIDX itself, as well time spent preparing to
build a MIDX bitmap.
These are limited to instrumenting the following functions:
- midx.c::find_commits_for_midx_bitmap()
- midx.c::midx_pack_order()
- midx.c::prepare_midx_packing_data()
- midx.c::write_midx_bitmap()
- midx.c::write_midx_internal()
- midx.c::write_midx_reverse_index()
to start and end with a trace2_region_enter() and trace2_region_leave(),
respectively.
The category for all of these is "midx", which matches the existing
convention. The region description matches the name of the function.
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'pack-bitmap-write.c')
0 files changed, 0 insertions, 0 deletions