{"thread":{"id":"63890","subject":"[PATCH] doc: fast-import: contextualize the hardware cost","startedAt":"2025-08-01T13:42:50Z","lastAt":"2025-08-01T14:44:20Z","messageCount":2,"participants":["kristofferhaugsbakk@fastmail.com","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"523204","messageId":"a9bc7547a27aab8bc2404caeb821b7f5c4c10d14.1754055658.git.code@khaugsbakk.name","threadId":"63890","inReplyTo":null,"subject":"[PATCH] doc: fast-import: contextualize the hardware cost","fromName":"","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-08-01T13:42:25Z","receivedAt":"2025-08-01T13:42:50Z","isPatch":true,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"From: Kristoffer Haugsbakk <code@khaugsbakk.name>\n\n6e411d20440 (Initial draft of fast-import documentation., 2007-02-05)\npointed out how much time a fast-import took on some hardware with a\nspecific cost.  Let’s further point out that this experiment was done\nin 2007.  So modern hardware should have no issues with such a repo.\n\nAlso move the parenthetical to the end now that it contains four words.\n\nSigned-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>\n---\n Documentation/git-fast-import.adoc | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-fast-import.adoc b/Documentation/git-fast-import.adoc\nindex d2327842003..6f9763c11b3 100644\n--- a/Documentation/git-fast-import.adoc\n+++ b/Documentation/git-fast-import.adoc\n@@ -182,7 +182,7 @@ amount of memory usage and processing time.  Assuming the frontend\n is able to keep up with fast-import and feed it a constant stream of data,\n import times for projects holding 10+ years of history and containing\n 100,000+ individual commits are generally completed in just 1-2\n-hours on quite modest (~$2,000 USD) hardware.\n+hours on quite modest hardware (~$2,000 USD in 2007).\n \n Most bottlenecks appear to be in foreign source data access (the\n source just cannot extract revisions fast enough) or disk IO (fast-import\n\nbase-commit: e813a0200a7121b97fec535f0d0b460b0a33356c\n-- \n2.50.1\n\n"},{"id":"523207","messageId":"xmqqo6szm799.fsf@gitster.g","threadId":"63890","inReplyTo":"a9bc7547a27aab8bc2404caeb821b7f5c4c10d14.1754055658.git.code@khaugsbakk.name","subject":"Re: [PATCH] doc: fast-import: contextualize the hardware cost","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-01T14:44:18Z","receivedAt":"2025-08-01T14:44:20Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"kristofferhaugsbakk@fastmail.com writes:\n\n> From: Kristoffer Haugsbakk <code@khaugsbakk.name>\n>\n> 6e411d20440 (Initial draft of fast-import documentation., 2007-02-05)\n> pointed out how much time a fast-import took on some hardware with a\n> specific cost.  Let’s further point out that this experiment was done\n> in 2007.  So modern hardware should have no issues with such a repo.\n>\n> Also move the parenthetical to the end now that it contains four words.\n>\n> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>\n> ---\n>  Documentation/git-fast-import.adoc | 2 +-\n>  1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/Documentation/git-fast-import.adoc b/Documentation/git-fast-import.adoc\n> index d2327842003..6f9763c11b3 100644\n> --- a/Documentation/git-fast-import.adoc\n> +++ b/Documentation/git-fast-import.adoc\n> @@ -182,7 +182,7 @@ amount of memory usage and processing time.  Assuming the frontend\n>  is able to keep up with fast-import and feed it a constant stream of data,\n>  import times for projects holding 10+ years of history and containing\n>  100,000+ individual commits are generally completed in just 1-2\n> -hours on quite modest (~$2,000 USD) hardware.\n> +hours on quite modest hardware (~$2,000 USD in 2007).\n\nThat is a definite improvement.  Thanks.\n"}]}