diff options
| author | Kristoffer Haugsbakk <code@khaugsbakk.name> | 2025-08-01 15:42:25 +0200 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2025-08-01 10:40:26 -0700 |
| commit | cca758d324acb0c4b8fd64e9d8792b3ee251ff76 (patch) | |
| tree | 2eda6d8cc59f69377235fd919e85f144ed32c03b | |
| parent | 54a3711a9dd968a04249beef157393d64b579d64 (diff) | |
| download | git-cca758d324acb0c4b8fd64e9d8792b3ee251ff76.tar.gz | |
doc: fast-import: contextualize the hardware cost
6e411d20440 (Initial draft of fast-import documentation., 2007-02-05)
pointed out how much time a fast-import took on some hardware with a
specific cost. Let’s further point out that this experiment was done
in 2007. So modern hardware should have no issues with such a repo.
Also move the parenthetical to the end now that it contains four words.
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rw-r--r-- | Documentation/git-fast-import.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt index 8b5dd6add0..77c88a18c6 100644 --- a/Documentation/git-fast-import.txt +++ b/Documentation/git-fast-import.txt @@ -182,7 +182,7 @@ amount of memory usage and processing time. Assuming the frontend is able to keep up with fast-import and feed it a constant stream of data, import times for projects holding 10+ years of history and containing 100,000+ individual commits are generally completed in just 1-2 -hours on quite modest (~$2,000 USD) hardware. +hours on quite modest hardware (~$2,000 USD in 2007). Most bottlenecks appear to be in foreign source data access (the source just cannot extract revisions fast enough) or disk IO (fast-import |