{"thread":{"id":"45140","subject":"git-p4.py caching","startedAt":"2017-02-14T18:17:41Z","lastAt":"2017-02-15T13:10:47Z","messageCount":2,"participants":["Martin-Louis Bright","Lars Schneider"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"311553","messageId":"CAG2PGsqs2dQM0SJ25ocHJ+Nex_m2NC5yQQuROxcF6SG2e93wCQ@mail.gmail.com","threadId":"45140","inReplyTo":null,"subject":"git-p4.py caching","fromName":"Martin-Louis Bright","fromEmail":"mlbright@gmail.com","sentAt":"2017-02-14T18:16:54Z","receivedAt":"2017-02-14T18:17:41Z","isPatch":false,"sender":{"key":"mlbright@gmail.com","avatar":null},"body":"hi!\n\nI am using git-p4.py to migrate a lot of medium and large Perforce\ndepots into git. I almost exclusively go one way: from Perforce to\ngit. I also frequently re-clone/re-migrate as the Perforce migration\nclient spec is refined.\n\nFor this, I have added rudimentary caching in git-p4.py so that\nPerforce requests are not repeated over the network.\n\nI have it working and tested on a ~150MB repo and the migration time was halved.\n\nIs this something that would be of interest to the larger community?\n\n--Martin\n"},{"id":"311647","messageId":"A8AD20AC-C069-4572-9C6A-519E1855220F@gmail.com","threadId":"45140","inReplyTo":"CAG2PGsqs2dQM0SJ25ocHJ+Nex_m2NC5yQQuROxcF6SG2e93wCQ@mail.gmail.com","subject":"Re: git-p4.py caching","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-02-15T13:10:37Z","receivedAt":"2017-02-15T13:10:47Z","isPatch":false,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 14 Feb 2017, at 19:16, Martin-Louis Bright <mlbright@gmail.com> wrote:\n\n[CC'ing Luke and George] \n\n\n> hi!\n> \n> I am using git-p4.py to migrate a lot of medium and large Perforce\n> depots into git. I almost exclusively go one way: from Perforce to\n> git. I also frequently re-clone/re-migrate as the Perforce migration\n> client spec is refined.\n> \n> For this, I have added rudimentary caching in git-p4.py so that\n> Perforce requests are not repeated over the network.\n\nMartin implemented an on disk cache and \"requests not repeated\" applies \nmostly for re-migrations. Re-migrations are multiple test migrations (\"git-p4 clone\") \nwith minor client spec changes until we find the right client spec for the\nproduction migration.\n\n> I have it working and tested on a ~150MB repo and the migration time was halved.\n> \n> Is this something that would be of interest to the larger community?\n\nI like the idea!\nDisclaimer: I work together with Martin on the P4 -> Git migrations :-)\n\nCheers,\nLars\n\n"}]}