From: "Mor, Gil (DXC Luxoft)" <gil.mor@dxc.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Git monorepo - recommendation regarding usage of sparse-checkout
Date: Tue, 30 May 2023 19:26:18 +0000 [thread overview]
Message-ID: <DS7PR01MB758914BD44E20CF8185B7C5BF64B9@DS7PR01MB7589.prod.exchangelabs.com> (raw)
Hello, we are experimenting with migrating a large-ish code base from SVN to a Git Monorepo and it would help us if we can get some input regarding the usage of sparse-checkout.
From our timing experiments sparse-checkout is the only method so far that reduces our times to good results.
The only issue might be the Disclaimer that the sparse-checkout feature is experimental, and that the behavior will change.
We have tried Full, Shallow, Blobless, Treeless clones in all combinations and it takes 25-40 minutes for each operation (checkout and branch switching).
Sparse checkouts reduce these times to a few minutes to checkout and a few seconds to switch branches for each sub-project/sparse set.
Our code base doesn't have binary blobs - only text.
Out of the high level use cases we would say B ("Users want a sparse working tree but are working in a larger whole") fits us.
https://git-scm.com/docs/sparse-checkout#_purpose_of_sparse_checkouts
The command is already featured in GitHub and GitLab articles about reducing Monorepos size but we are still not sure how un/stable the feature is or how commonly used the feature is already.
So, we thought we'll write an email to see if we can get a bit more nuanced answer about the safety of real-world usage so that we can make an informed decision whether or not to start using sparse-checkout, despite it being experimental.
We are not looking for 100% assurance, we know the responsibility is eventually totally ours and there are no guarantees, but it seems like a game changer so we are just looking for a bit more information so that we can make a decision.
Best Regards,
Gil Mor
SW Developer
Cross Industry Solutions
Luxoft
A DXC Company
next reply other threads:[~2023-05-30 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 19:26 Mor, Gil (DXC Luxoft) [this message]
2023-07-09 1:44 ` Git monorepo - recommendation regarding usage of sparse-checkout Sean Allred
2023-07-27 20:01 ` Rudy Rigot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DS7PR01MB758914BD44E20CF8185B7C5BF64B9@DS7PR01MB7589.prod.exchangelabs.com \
--to=gil.mor@dxc.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).