aboutsummaryrefslogtreecommitdiff
path: root/environment.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2011-07-06 19:08:55 -0700
committerJunio C Hamano <gitster@pobox.com>2011-07-06 19:09:29 -0700
commit5f44324d88a6a6699bc30912b26784ac0ade638d (patch)
treec37f1a687887fc003ce4d59fd3251201aba64b30 /environment.c
parent033c2dc4364042b9e6dbd44e82e1974f78a72567 (diff)
downloadgit-5f44324d88a6a6699bc30912b26784ac0ade638d.tar.gz
git-5f44324d88a6a6699bc30912b26784ac0ade638d.tar.xz
core: log offset pack data accesses happened
In a workload other than "git log" (without pathspec nor any option that causes us to inspect trees and blobs), the recency pack order is said to cause the access jump around quite a bit. Add a hook to allow us observe how bad it is. "git config core.logpackaccess /var/tmp/pal.txt" will give you the log in the specified file. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'environment.c')
-rw-r--r--environment.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/environment.c b/environment.c
index 94d58fd24..19351024f 100644
--- a/environment.c
+++ b/environment.c
@@ -36,6 +36,7 @@ size_t packed_git_window_size = DEFAULT_PACKED_GIT_WINDOW_SIZE;
size_t packed_git_limit = DEFAULT_PACKED_GIT_LIMIT;
size_t delta_base_cache_limit = 16 * 1024 * 1024;
unsigned long big_file_threshold = 512 * 1024 * 1024;
+const char *log_pack_access;
const char *pager_program;
int pager_use_color = 1;
const char *editor_program;