From: "René Scharfe" <l.s.r@web.de>
To: Git List <git@vger.kernel.org>
Cc: "Andrzej Hunt" <andrzej@ahunt.org>, "Eric Wong" <e@80x24.org>,
"Jeff King" <peff@peff.net>, "Junio C Hamano" <gitster@pobox.com>,
"Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: [PATCH] hash: reduce size of algo member of object ID
Date: Sun, 3 Oct 2021 07:51:40 +0200 [thread overview]
Message-ID: <8da7bad2-b5a8-5aef-284b-dfa4e78556a9@web.de> (raw)
cf0983213c (hash: add an algo member to struct object_id, 2021-04-26)
introduced the algo member as an int. This increased the size of struct
object_id by 4 bytes (12.5%) and imposed a 4-byte alignment. Currently
we only need to stored the values 0, 1 and 2 in it. Let's use an
unsigned char instead to reduce the size overhead and lift the alignment
requirement.
Signed-off-by: René Scharfe <l.s.r@web.de>
---
Not sure how to measure the performance impact of this change. The perf
tests mentioned by cf0983213c don't show much of a difference with
GIT_PERF_REPEAT_COUNT=10 for me:
Test origin/master HEAD
--------------------------------------------------------------------------------------------
0001.1: rev-list --all 0.11(0.08+0.02) 0.11(0.08+0.02) +0.0%
0001.2: rev-list --all --objects 3.04(2.98+0.05) 3.04(2.98+0.05) +0.0%
0001.3: rev-list --parents 0.05(0.04+0.01) 0.05(0.03+0.01) +0.0%
0001.5: rev-list -- dummy 0.21(0.20+0.01) 0.21(0.19+0.01) +0.0%
0001.6: rev-list --parents -- dummy 0.22(0.20+0.01) 0.22(0.20+0.01) +0.0%
0001.8: rev-list $commit --not --all 0.06(0.05+0.00) 0.06(0.05+0.00) +0.0%
0001.9: rev-list --objects $commit --not --all 0.06(0.05+0.00) 0.06(0.05+0.00) +0.0%
1450.1: fsck 20.20(19.71+0.47) 20.18(19.70+0.48) -0.1%
hash.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hash.h b/hash.h
index 9e25c40e9a..24d8f7cd21 100644
--- a/hash.h
+++ b/hash.h
@@ -115,7 +115,7 @@ static inline void git_SHA256_Clone(git_SHA256_CTX *dst, const git_SHA256_CTX *s
struct object_id {
unsigned char hash[GIT_MAX_RAWSZ];
- int algo; /* XXX requires 4-byte alignment */
+ unsigned char algo;
};
/* A suitably aligned type for stack allocations of hash contexts. */
--
2.33.0
next reply other threads:[~2021-10-03 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 5:51 René Scharfe [this message]
2021-10-04 7:31 ` [PATCH] hash: reduce size of algo member of object ID Eric Wong
2021-10-04 8:13 ` Jeff King
2021-10-04 8:20 ` Jeff King
2021-10-05 0:04 ` brian m. carlson
2021-10-05 17:28 ` René Scharfe
2021-10-04 8:47 ` Ævar Arnfjörð Bjarmason
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=8da7bad2-b5a8-5aef-284b-dfa4e78556a9@web.de \
--to=l.s.r@web.de \
--cc=andrzej@ahunt.org \
--cc=carenas@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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;
as well as URLs for NNTP newsgroup(s).