From: Lars Schneider <larsxschneider@gmail.com>
To: Martin-Louis Bright <mlbright@gmail.com>
Cc: Git List <git@vger.kernel.org>, Luke Diamand <luke@diamand.org>,
George Vanburgh <george@vanburgh.me>
Subject: Re: git-p4.py caching
Date: Wed, 15 Feb 2017 14:10:37 +0100 [thread overview]
Message-ID: <A8AD20AC-C069-4572-9C6A-519E1855220F@gmail.com> (raw)
In-Reply-To: <CAG2PGsqs2dQM0SJ25ocHJ+Nex_m2NC5yQQuROxcF6SG2e93wCQ@mail.gmail.com>
> On 14 Feb 2017, at 19:16, Martin-Louis Bright <mlbright@gmail.com> wrote:
[CC'ing Luke and George]
> hi!
>
> I am using git-p4.py to migrate a lot of medium and large Perforce
> depots into git. I almost exclusively go one way: from Perforce to
> git. I also frequently re-clone/re-migrate as the Perforce migration
> client spec is refined.
>
> For this, I have added rudimentary caching in git-p4.py so that
> Perforce requests are not repeated over the network.
Martin implemented an on disk cache and "requests not repeated" applies
mostly for re-migrations. Re-migrations are multiple test migrations ("git-p4 clone")
with minor client spec changes until we find the right client spec for the
production migration.
> I have it working and tested on a ~150MB repo and the migration time was halved.
>
> Is this something that would be of interest to the larger community?
I like the idea!
Disclaimer: I work together with Martin on the P4 -> Git migrations :-)
Cheers,
Lars
prev parent reply other threads:[~2017-02-15 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 18:16 git-p4.py caching Martin-Louis Bright
2017-02-15 13:10 ` Lars Schneider [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A8AD20AC-C069-4572-9C6A-519E1855220F@gmail.com \
--to=larsxschneider@gmail.com \
--cc=george@vanburgh.me \
--cc=git@vger.kernel.org \
--cc=luke@diamand.org \
--cc=mlbright@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).