•  
      request #5704 Pushing GIT repo take a very long time
    Infos
    #5704
    Manuel Vacelet (vaceletm)
    2013-12-10 19:42
    2013-12-06 13:51
    5815
    Details
    Pushing GIT repo take a very long time
    The clone binutils-gdb.git from the external repo tooks less than 10 minutes but the end-user have now been waiting over 24 hours to push the clone into our tuleap instance.

    The total size of the clone is 229Mbytes (and 38 files). Following is the output of "git fsck --full":
    Checking object directories: 100% (256/256), done.
    Checking objects: 100% (844664/844664), done.
    Checking connectivity: 843724, done
    SCM/Git
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Manuel Vacelet (vaceletm)
    Closed
    Empty
    Attachments
    Empty
    References

    Follow-ups

    User avatar
    One of the blockers here is the post processing.
    The patch in review (gerrit #1553) add an hard limit of post processing of references (threshold set at 100)

    It means that, when a push contains more than 100 references (100 branches or tags) only the first 100 references will be processed (email, trigger of CI jobs, reference extraction, logs & co).
    All the data will be recorded onto the filesystem in the git repository but we limit the further processing.

    I was able to push "repo" (the android tool) in ~15 minutes with this patch.

    • Status changed from New to Under review