From: "Marco Costalba" <mcostalba@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: [WISH] Store also tag dereferences in packed-refs
Date: Sat, 18 Nov 2006 10:15:12 +0100 [thread overview]
Message-ID: <e5bfff550611180115j135746a1h916e8ae029d1374d@mail.gmail.com> (raw)
Time needed to execute git-peek-remote in my box with cold cache currently is:
- git tree 2.347 ms
- linux tree 2.144 ms
And refs are *already* packed in both repos.
Looking at packed-refs file, it contains something like:
d9b0f913ce0508fcc83e642e0241f373428368e5 refs/tags/v1.4.3
4314f5982d2aac08001a977fc0b1b611e858e025 refs/tags/v1.4.3-rc1
while I would need something like git-peek-remote output,
d9b0f913ce0508fcc83e642e0241f373428368e5 refs/tags/v1.4.3
e0b0830726286287744cc9e1a629a534bbe75452 refs/tags/v1.4.3^{}
4314f5982d2aac08001a977fc0b1b611e858e025 refs/tags/v1.4.3-rc1
1965efb1599f59b8e3380335d1fa395e2008a30b refs/tags/v1.4.3-rc1^{}
Because the sha value a tag points to is needed to match against
git-rev-list output so to identify tagged revisions.
Would be possible to store in packed-refs also the dereferenced tag
info, so that cold opening of a repository would be much faster?
Just to give an idea, with warmed up cache, refs reading times are:
- git tree 43 ms
- linux tree 28 ms
Thanks
Marco
P.S: In case it's not clear I don't suggest to read directly the
packed-refs file with the added info, but always to use
next reply other threads:[~2006-11-18 9:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 9:15 Marco Costalba [this message]
2006-11-18 18:38 ` [WISH] Store also tag dereferences in packed-refs Junio C Hamano
2006-11-18 18:43 ` Petr Baudis
2006-11-18 18:47 ` Marco Costalba
2006-11-18 19:04 ` Junio C Hamano
2006-11-19 0:28 ` Marco Costalba
2006-11-19 1:11 ` Linus Torvalds
2006-11-19 1:40 ` Junio C Hamano
2006-11-19 1:45 ` Junio C Hamano
2006-11-19 1:59 ` Linus Torvalds
2006-11-19 9:40 ` Marco Costalba
2006-11-19 18:05 ` Linus Torvalds
2006-11-19 19:07 ` Marco Costalba
2006-11-19 20:09 ` Marco Costalba
2006-11-19 20:36 ` Linus Torvalds
2006-11-19 20:44 ` Linus Torvalds
2006-11-19 21:01 ` Junio C Hamano
2006-11-19 21:14 ` Linus Torvalds
2006-11-19 21:24 ` Jakub Narebski
2006-11-19 23:36 ` Linus Torvalds
2006-11-20 2:35 ` Junio C Hamano
2006-11-20 9:40 ` Jakub Narebski
2006-11-20 12:56 ` Marco Costalba
2006-11-20 16:29 ` Linus Torvalds
2006-11-20 19:32 ` Junio C Hamano
2006-11-19 22:25 ` Marco Costalba
2006-11-19 23:26 ` Linus Torvalds
2006-11-19 20:18 ` Linus Torvalds
[not found] ` <200611201154.08732.jnareb@gmail.com>
[not found] ` <7vu00u2wln.fsf@assigned-by-dhcp.cox.net>
2006-11-20 11:33 ` Jakub Narebski
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=e5bfff550611180115j135746a1h916e8ae029d1374d@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).