Closed (fixed)
Project:
Version Control API -- Git backend
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
26 Mar 2014 at 14:00 UTC
Updated:
1 May 2014 at 04:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
marvil07 commentedComment #2
marvil07 commentedI'm testing this patch in git7site doing a fullsync via drush with drupal core repository, which is a really big repository for our standards. Hopefully it's good enough.
Comment #3
marvil07 commentedSadly not enough yet:
Comment #5
marvil07 commentedJust an update about the last additions:
I could finally sync core. Notice sometimes it need to be run several times to get it right, but it seems to be better at memory usage.
Sadly, core sandboxes has lots of commits pending to read, and that's a lot of exec's, and a lot of time.
Maybe it is now working, but I cannot know now, since git7site is being re-initiated daily.
I will try again with imp which is way behind(last time after ~14hours if failed because of re-synchronization), and see how it goes.
Hopefully there is still something else I can do to improve performance, but for now exec's are taking most of the time in the run.
Maybe it is time to implement #973890: Create a reposync plugin using libgit2 php binding(use a php binding of a c library to access git data) or #1019976: Improve performance of log parser(use git-fast-export to avoid most of git calls on initial synchronization, and force flushing on big repositories or the ones with a lot of data pending to be sync, i.e. imp)?
Comment #6
marvil07 commentedLet's call this fixed for now.
What I had tried on git7site:
So, i. e. IMP sandbox probably will take a lot of time, but I guess it will eventually succeed.