From: Junio C Hamano <gitster@pobox.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: Phillip Wood <phillip.wood@dunelm.org.uk>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] xdiff: optimize xdl_hash_record_verbatim
Date: Wed, 20 Aug 2025 14:34:52 -0700 [thread overview]
Message-ID: <xmqq7byx8yo3.fsf@gitster.g> (raw)
In-Reply-To: <0379ba2d-837b-761e-9d5a-d65ca9d051d6@ispras.ru> (Alexander Monakov's message of "Tue, 12 Aug 2025 20:56:37 +0300 (MSK)")
Alexander Monakov <amonakov@ispras.ru> writes:
>> On Mon, 11 Aug 2025, Phillip Wood wrote:
>>
>> > > That's what the 'cycles' column in the table gives (6.21/5.8 = 1.070...)
>> >
>> > It would be helpful to add a column with those calculations in it rather than
>> > forcing the reader to calculate the speed up for themselves.
>>
>> Ok, will change it to
>>
>> version | speedup over (A) | cycles, bn | instructions, bn
>> ----------------------------------------------------------
>> A 6.38 11.3
>> B 1.027 6.21 10.89
>> C 1.1 5.80 9.95
>> D 1.094 5.83 8.74
>> ----------------------------------------------------------
>
> On my Skylake:
>
> version | speedup over (A) | cycles, bn | instructions, bn
> ----------------------------------------------------------
> A 5.77 10.96
> B 1.076 5.36 10.60
> C 1.12 5.16 9.66
> ----------------------------------------------------------
>
> A is today's master, B and C are patch 1 and 1+2 like before.
The thread has gone quiet. I assume everybody is happy with the
result? Can we have a hopefully final v2 iteration of these
patches, to address the updated to the table (this thread), to
squelch the __asm__() issue [*asm*], and a reword you mentioned
[*reword*] against Phillip's review?
Thanks.
*asm*
https://lore.kernel.org/git/3405f274-cef1-b361-7424-840dc55b48a1@ispras.ru/
*reword*
https://lore.kernel.org/git/353c7865-d9b5-2a1c-4d71-cd1136581f01@ispras.ru/
next prev parent reply other threads:[~2025-08-20 21:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 19:05 [PATCH 0/2] optimize string hashing in xdiff Alexander Monakov
2025-07-28 19:05 ` [PATCH 1/2] xdiff: refactor xdl_hash_record() Alexander Monakov
2025-07-28 19:05 ` [PATCH 2/2] xdiff: optimize xdl_hash_record_verbatim Alexander Monakov
2025-07-28 20:50 ` Junio C Hamano
2025-07-28 20:57 ` Alexander Monakov
2025-08-04 13:49 ` Phillip Wood
2025-08-04 14:39 ` Alexander Monakov
2025-08-11 13:13 ` Phillip Wood
2025-08-11 14:14 ` Alexander Monakov
2025-08-12 17:56 ` Alexander Monakov
2025-08-20 21:34 ` Junio C Hamano [this message]
2025-09-08 19:06 ` Alexander Monakov
2025-09-08 21:04 ` Junio C Hamano
2025-08-13 13:10 ` Phillip Wood
2025-07-28 19:32 ` [PATCH 0/2] optimize string hashing in xdiff Junio C Hamano
2025-07-28 19:56 ` Eli Schwartz
2025-07-28 20:54 ` Junio C Hamano
2025-07-28 20:25 ` Alexander Monakov
2025-08-14 15:01 ` Junio C Hamano
2025-08-28 23:40 ` Junio C Hamano
2025-08-29 1:13 ` Jacob Keller
2025-08-29 3:09 ` Elijah Newren
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=xmqq7byx8yo3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=amonakov@ispras.ru \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.