From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: friel@openai.com, git@vger.kernel.org
Subject: Re: [PATCH v2] pack-objects: trace pack bytes written
Date: Thu, 20 Aug 2026 20:33:53 -0700 [thread overview]
Message-ID: <xmqqlda0rvtq.fsf@gitster.g> (raw)
In-Reply-To: <20260821004739.GA297273@coredump.intra.peff.net> (Jeff King's message of "Thu, 20 Aug 2026 20:47:39 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Aug 19, 2026 at 04:28:10PM -0700, friel@openai.com wrote:
>
>> From: Friel <friel@openai.com>
>>
>> We want to measure how compression settings affect push performance on
>> the client. Different settings can produce different-sized packs from
>> the same objects. Trace2 records the object count, but we also need the
>> pack size to compare those settings.
>>
>> Add a write_pack_file/wrote_bytes Trace2 datum alongside
>> write_pack_file/wrote. Count packs written to stdout or disk, including
>> each pack's header and trailing checksum. When pack.packSizeLimit splits
>> the output, report the sum of the pack sizes.
>>
>> Signed-off-by: Friel <friel@openai.com>
>> ---
>> Junio, you're right. Updating bytes_written before finalization is
>> equivalent. I've dropped pack_bytes; everything else is unchanged.
>> Thanks.
>
> The downthread discussion went pretty far off-topic, so for those who do
> not want to read it, the summary is: this patch looks good to me. ;)
It looks good to me, too. Thanks, all.
prev parent reply other threads:[~2026-08-21 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 23:39 [PATCH] pack-objects: trace pack bytes written friel
2026-08-18 1:08 ` Junio C Hamano
2026-08-19 23:28 ` [PATCH v2] " friel
2026-08-20 5:41 ` Patrick Steinhardt
2026-08-20 8:21 ` Jeff King
2026-08-20 9:13 ` Patrick Steinhardt
2026-08-21 0:40 ` Jeff King
2026-08-21 3:33 ` Junio C Hamano
2026-08-20 15:35 ` Junio C Hamano
2026-08-21 0:47 ` Jeff King
2026-08-21 3:33 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlda0rvtq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=friel@openai.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox