git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] doc: fast-import: contextualize the hardware cost

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 1, 2025, 14:44 UTC
Message-ID
<xmqqo6szm799.fsf@gitster.g>
In-Reply-To
<a9bc7547a27aab8bc2404caeb821b7f5c4c10d14.1754055658.git.code@khaugsbakk.name>
kristofferhaugsbakk@fastmail.com writes:
Show 24 quoted lines
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> 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>
> ---
>  Documentation/git-fast-import.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-fast-import.adoc b/Documentation/git-fast-import.adoc
> index d2327842003..6f9763c11b3 100644
> --- a/Documentation/git-fast-import.adoc
> +++ b/Documentation/git-fast-import.adoc
> @@ -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).
That is a definite improvement.  Thanks.
Previous: kristofferhaugsbakk@fastmail.com
Message 2 of 2 in “doc: fast-import: contextualize the hardware cost”
  1. doc: fast-import: contextualize the hardware costkristofferhaugsbakk@fastmail.com, Aug 1, 2025
  2. Junio C HamanoAug 1, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.