git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Why is "git tag --contains" so slow?

From
Jeff King <peff@peff.net>
Date
Jul 1, 2010, 15:38 UTC
Message-ID
<20100701153842.GA15466@sigill.intra.peff.net>
In-Reply-To
<20100701150331.GA12851@sigill.intra.peff.net>
On Thu, Jul 01, 2010 at 11:03:31AM -0400, Jeff King wrote:
Show 15 quoted lines
>   $ time git tag --contains HEAD~200
>   v1.7.1
>   v1.7.1-rc2
>   v1.7.1.1
>   v1.7.2-rc0
>   v1.7.2-rc1
> 
>   real    0m2.179s
>   user    0m2.156s
>   sys     0m0.020s
>
> [...]
>
> I suspect we could do even better by sharing information between
> traversals. That is, walk the graph from each ref, but retain marks on

Here is a quick and dirty patch to implement what I suggested. With it, I get the same results as above, but it runs between 3 and 4 times as fast:

  real    0m0.621s
  user    0m0.588s
  sys     0m0.032s

Implementing the timestamp-checking thing that name-rev does would probably drop it even more (at the expense of less accuracy in the face of clock skew).

diff --git a/builtin/tag.c b/builtin/tag.c
index d311491..d18c3ed 100644
--- a/builtin/tag.c
+++ b/builtin/tag.c
@@ -10,6 +10,8 @@
 #include "builtin.h"
 #include "refs.h"
 #include "tag.h"
+#include "diff.h"
+#include "revision.h"
 #include "run-command.h"
 #include "parse-options.h"
 
@@ -31,6 +33,42 @@ struct tag_filter {
 
 #define PGP_SIGNATURE "-----BEGIN PGP SIGNATURE-----"
 
+static int in_commit_list(const struct commit_list *want, struct commit *c)
+{
+	for (; want; want = want->next)
+		if (!hashcmp(want->item->object.sha1, c->object.sha1))
+			return 1;
+	return 0;
+}
+
+static int contains(const struct commit_list *want, struct commit *candidate)
+{
+	struct commit_list *p;
+
+	/* was it previously marked as containing a want commit? */
+	if (candidate->object.flags & TMP_MARK)
+		return 1;
+	/* or marked as not possibly containing a want commit? */
+	if (candidate->object.flags & UNINTERESTING)
+		return 0;
+	/* or are we it? */
+	if (in_commit_list(want, candidate))
+		return 1;
+
+	/* If not, then try parents, and be sure to mark ourselves
+	 * for future traversals. */
+	parse_commit(candidate);
+	for (p = candidate->parents; p; p = p->next) {
+		if (contains(want, p->item)) {
+			candidate->object.flags |= TMP_MARK;
+			return 1;
+		}
+	}
+
+	candidate->object.flags |= UNINTERESTING;
+	return 0;
+}
+
 static int show_reference(const char *refname, const unsigned char *sha1,
 			  int flag, void *cb_data)
 {
@@ -49,7 +87,7 @@ static int show_reference(const char *refname, const unsigned char *sha1,
 			commit = lookup_commit_reference_gently(sha1, 1);
 			if (!commit)
 				return 0;
-			if (!is_descendant_of(commit, filter->with_commit))
+			if (!contains(filter->with_commit, commit))
 				return 0;
 		}
 
Previous: Jeff KingNext: tytso@mit.edu
Message 7 of 46 in “Why is "git tag --contains" so slow?”
  1. Theodore Ts'oJul 1, 2010
  2. Shawn O. PearceJul 1, 2010
  3. Sam VilainJul 3, 2010
  4. Avery PennarunJul 1, 2010
  5. tytso@mit.eduJul 1, 2010
  6. Jeff KingJul 1, 2010
  7. Jeff KingJul 1, 2010
  8. tytso@mit.eduJul 2, 2010
  9. Jeff KingJul 3, 2010
  10. tytso@mit.eduJul 4, 2010
  11. Jeff KingJul 5, 2010
  12. 1/4 tag: speed up --contains calculationJeff King, Jul 5, 2010
  13. Jonathan NiederOct 13, 2010
  14. Clemens BuchacherOct 13, 2010
  15. Ævar Arnfjörð BjarmasonFeb 23, 2011
  16. Jeff KingFeb 23, 2011
  17. 2/4 limit "contains" traversals based on commit timestampJeff King, Jul 5, 2010
  18. Jonathan NiederOct 13, 2010
  19. 3/4 default core.clockskew variable to one dayJeff King, Jul 5, 2010
  20. 4/4 name-rev: respect core.clockskewJeff King, Jul 5, 2010
  21. Jeff KingJul 5, 2010
  22. Jonathan NiederOct 14, 2010
  23. Clemens BuchacherOct 16, 2010
  24. Jeff KingOct 27, 2010
  25. Clemens BuchacherOct 28, 2010
  26. tytso@mit.eduJul 5, 2010
  27. Jeff KingJul 6, 2010
  28. Will PalmerJul 6, 2010
  29. tytso@mit.eduJul 6, 2010
  30. Jeff KingJul 8, 2010
  31. Will PalmerJul 8, 2010
  32. tytso@mit.eduJul 8, 2010
  33. Jeff KingJul 7, 2010
  34. Theodore TsoJul 8, 2010
  35. Jakub NarebskiJul 8, 2010
  36. Nicolas PitreJul 8, 2010
  37. Avery PennarunJul 8, 2010
  38. Nicolas PitreJul 8, 2010
  39. Jakub NarebskiJul 8, 2010
  40. Sverre RabbelierJul 8, 2010
  41. Nicolas PitreJul 8, 2010
  42. Nicolas PitreJul 8, 2010
  43. Jeff KingJul 8, 2010
  44. Johan HerlandJul 8, 2010
  45. Nicolas PitreJul 8, 2010
  46. Jeff KingJul 7, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.