Skip to content

Commit cca758d

Browse files
LemmingAvalanchegitster
authored andcommitted
doc: fast-import: contextualize the hardware cost
6e411d2 (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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 54a3711 commit cca758d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Documentation/git-fast-import.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ amount of memory usage and processing time. Assuming the frontend
182182
is able to keep up with fast-import and feed it a constant stream of data,
183183
import times for projects holding 10+ years of history and containing
184184
100,000+ individual commits are generally completed in just 1-2
185-
hours on quite modest (~$2,000 USD) hardware.
185+
hours on quite modest hardware (~$2,000 USD in 2007).
186186

187187
Most bottlenecks appear to be in foreign source data access (the
188188
source just cannot extract revisions fast enough) or disk IO (fast-import

0 commit comments

Comments
 (0)