[PATCH v2 1/7] Documentation: deltaBaseCacheLimit is per-thread
- From
- Jonathan Tan <jonathantanmy@google.com>
- Date
- Sep 8, 2020, 19:48 UTC
- Message-ID
- <fe79905660bb11a88f605713cd132cbde46ec8a5.1599594441.git.jonathantanmy@google.com>
- In-Reply-To
- <cover.1599594441.git.jonathantanmy@google.com>
Clarify that core.deltaBaseCacheLimit is per-thread, as can be seen from the fact that cache usage (base_cache_used in struct thread_local in builtin/index-pack.c) is tracked individually for each thread and compared against delta_base_cache_limit.
Signed-off-by: Jonathan Tan <jonathantanmy@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> --- Documentation/config/core.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/config/core.txt b/Documentation/config/core.txt index 74619a9c03..02002cf109 100644 --- a/Documentation/config/core.txt +++ b/Documentation/config/core.txt @@ -399,7 +399,7 @@ the largest projects. You probably do not need to adjust this value. Common unit suffixes of 'k', 'm', or 'g' are supported. core.deltaBaseCacheLimit:: - Maximum number of bytes to reserve for caching base objects + Maximum number of bytes per thread to reserve for caching base objects that may be referenced by multiple deltified objects. By storing the entire decompressed base objects in a cache Git is able to avoid unpacking and decompressing frequently used base
-- 2.28.0.526.ge36021eeef-goog