summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 896f7e3)
raw | patch | inline | side by side (parent: 896f7e3)
author | Jeff King <peff@peff.net> | |
Mon, 5 Jul 2010 12:34:19 +0000 (08:34 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Mon, 5 Jul 2010 19:12:20 +0000 (12:12 -0700) |
When looking for commits that contain other commits (e.g.,
via "git tag --contains"), we can end up traversing useless
portions of the graph. For example, if I am looking for a
tag that contains a commit made last week, there is not much
point in traversing portions of the history graph made five
years ago.
This optimization can provide massive speedups. For example,
doing "git tag --contains HEAD~200" in the linux-2.6
repository goes from:
real 0m5.302s
user 0m5.116s
sys 0m0.184s
to:
real 0m0.030s
user 0m0.020s
sys 0m0.008s
The downside is that we will no longer find some answers in
the face of extreme clock skew, as we will stop the
traversal early when seeing commits skewed too far into the
past.
Name-rev already implements a similar optimization, using a
"slop" of one day to allow for a certain amount of clock
skew in commit timestamps. This patch introduces a
"core.clockskew" variable, which allows specifying the
allowable amount of clock skew in seconds. For safety, it
defaults to "none", causing a full traversal (i.e., no
change in behavior from previous versions).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
via "git tag --contains"), we can end up traversing useless
portions of the graph. For example, if I am looking for a
tag that contains a commit made last week, there is not much
point in traversing portions of the history graph made five
years ago.
This optimization can provide massive speedups. For example,
doing "git tag --contains HEAD~200" in the linux-2.6
repository goes from:
real 0m5.302s
user 0m5.116s
sys 0m0.184s
to:
real 0m0.030s
user 0m0.020s
sys 0m0.008s
The downside is that we will no longer find some answers in
the face of extreme clock skew, as we will stop the
traversal early when seeing commits skewed too far into the
past.
Name-rev already implements a similar optimization, using a
"slop" of one day to allow for a certain amount of clock
skew in commit timestamps. This patch introduces a
"core.clockskew" variable, which allows specifying the
allowable amount of clock skew in seconds. For safety, it
defaults to "none", causing a full traversal (i.e., no
change in behavior from previous versions).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
cache.h | patch | blob | history | |
commit.c | patch | blob | history | |
config.c | patch | blob | history |
index c9fa3df7f5b343ecea980ceb423e7c23d2eb22b2..2dfb636ccaad87962c848feadabddaee7ac36ab3 100644 (file)
--- a/cache.h
+++ b/cache.h
extern int fsync_object_files;
extern int core_preload_index;
extern int core_apply_sparse_checkout;
+extern int core_clock_skew;
enum safe_crlf {
SAFE_CRLF_FALSE = 0,
diff --git a/commit.c b/commit.c
index 20354c6f1c4e601520103cf7b832b114c3e4c369..c849b50797e09734d53e5dce1bbc5483f5dbe092 100644 (file)
--- a/commit.c
+++ b/commit.c
#include "revision.h"
#include "notes.h"
+int core_clock_skew = -1;
int save_commit_buffer = 1;
const char *commit_type = "commit";
}
static int contains_recurse(struct commit *candidate,
- const struct commit_list *want)
+ const struct commit_list *want,
+ unsigned long cutoff)
{
struct commit_list *p;
if (parse_commit(candidate) < 0)
return 0;
+ /* stop searching if we go too far back in time */
+ if (candidate->date < cutoff)
+ return 0;
+
/* Otherwise recurse and mark ourselves for future traversals. */
for (p = candidate->parents; p; p = p->next) {
- if (contains_recurse(p->item, want)) {
+ if (contains_recurse(p->item, want, cutoff)) {
candidate->object.flags |= TMP_MARK;
return 1;
}
int contains(struct commit *candidate, const struct commit_list *want)
{
- return contains_recurse(candidate, want);
+ unsigned long cutoff = 0;
+
+ if (core_clock_skew >= 0) {
+ const struct commit_list *c;
+ unsigned long min_date = ULONG_MAX;
+ for (c = want; c; c = c->next) {
+ if (parse_commit(c->item) < 0)
+ continue;
+ if (c->item->date < min_date)
+ min_date = c->item->date;
+ }
+ if (min_date > core_clock_skew)
+ cutoff = min_date - core_clock_skew;
+ }
+
+ return contains_recurse(candidate, want, cutoff);
}
diff --git a/config.c b/config.c
index cdcf5836c6c374eb59e80f89dbcf525fd6bf780f..7a18bc95ae007cd1a8a7636e34a12f3c78b1039b 100644 (file)
--- a/config.c
+++ b/config.c
return 0;
}
+ if (!strcmp(var, "core.clockskew")) {
+ if (!value || !strcmp(value, "none"))
+ core_clock_skew = -1;
+ else
+ core_clock_skew = git_config_int(var, value);
+ return 0;
+ }
+
/* Add other config variables here and to Documentation/config.txt. */
return 0;
}