* [PATCH] doc: fast-import: contextualize the hardware cost
@ 2025-08-01 13:42 kristofferhaugsbakk
2025-08-01 14:44 ` Junio C Hamano
0 siblings, 1 reply; 2+ messages in thread
From: kristofferhaugsbakk @ 2025-08-01 13:42 UTC (permalink / raw)
To: git; +Cc: Kristoffer Haugsbakk
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).
Most bottlenecks appear to be in foreign source data access (the
source just cannot extract revisions fast enough) or disk IO (fast-import
base-commit: e813a0200a7121b97fec535f0d0b460b0a33356c
--
2.50.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] doc: fast-import: contextualize the hardware cost
2025-08-01 13:42 [PATCH] doc: fast-import: contextualize the hardware cost kristofferhaugsbakk
@ 2025-08-01 14:44 ` Junio C Hamano
0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2025-08-01 14:44 UTC (permalink / raw)
To: kristofferhaugsbakk; +Cc: git, Kristoffer Haugsbakk
kristofferhaugsbakk@fastmail.com writes:
> 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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-08-01 14:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-01 13:42 [PATCH] doc: fast-import: contextualize the hardware cost kristofferhaugsbakk
2025-08-01 14:44 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).