Skip to content
Snippets Groups Projects
This project is mirrored from https://:*****@gitlab.com/gitlab-org/omnibus-gitlab.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
  1. Sep 13, 2019
  2. Sep 12, 2019
  3. Sep 06, 2019
  4. Sep 05, 2019
  5. Sep 03, 2019
  6. Aug 30, 2019
    • Stan Hu's avatar
      Fix slow fetches for repositories using object deduplication · 52bf3a15
      Stan Hu authored
      In https://gitlab.com/gitlab-org/gitaly/merge_requests/1297, we
      introduced a mechanism to prevent accidental deletion of objects from
      object pools. The idea is that if an object becomes "dangling", meaning
      there is no ref pointing to it, we just add a new ref to un-dangle
      it. It turns out this can create too many refs.
      
      If a pooled repository may contain many dangling references, a fetch
      from the parent repository to one of its fork may take an
      extraordinarily long time because git will attempt to run `git
      for-each-ref` on every single ref in the pooled repository. This can
      cause a simple fetch to take minutes.
      
      To avoid this problem, we use a similar strategy that we employed in the
      `git push` case
      (https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3364).  Git
      added a config option, core.alternateRefsCommand, to fix this issue.
      From
      https://github.com/git/git/commit/465e73fff380808f0ba3fb17984ab8636afb6405:
      
      When pushing into a repository that borrows its objects from an
      alternate object store, "git receive-pack" that responds to the push
      request on the other side lists the tips of refs in the alternate to
      reduce the amount of objects transferred.  This sometimes is detrimental
      when the number of refs in the alternate is absurdly large, in which
      case the bandwidth saved in potentially fewer objects transferred is
      wasted in excessively large ref advertisement.  The alternate refs that
      are advertised are now configurable with a pair of configuration
      variables.
      
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65985
      52bf3a15
  7. Aug 23, 2019
  8. Aug 22, 2019
  9. Aug 14, 2019
  10. Aug 13, 2019
  11. Aug 07, 2019
  12. Jul 31, 2019
  13. Jul 25, 2019
  14. Jul 12, 2019
  15. Jul 11, 2019
  16. Jul 09, 2019
  17. Jun 28, 2019
  18. Jun 27, 2019
  19. Jun 21, 2019
    • Stan Hu's avatar
      Fix slow pushes for repositories using object deduplication · d8b2ed54
      Stan Hu authored
      On GitLab.com, we noticed pushes to the GitLab CE and EE repositories
      were taking 3-4 minutes because they were advertising thousands of refs
      from forked repositories..
      
      Git added a config option, core.alternateRefsPrefixes, to fix that
      issue.  From
      https://github.com/git/git/commit/465e73fff380808f0ba3fb17984ab8636afb6405:
      
      When pushing into a repository that borrows its objects from an
      alternate object store, "git receive-pack" that responds to the push
      request on the other side lists the tips of refs in the alternate to
      reduce the amount of objects transferred.  This sometimes is detrimental
      when the number of refs in the alternate is absurdly large, in which
      case the bandwidth saved in potentially fewer objects transferred is
      wasted in excessively large ref advertisement.  The alternate refs that
      are advertised are now configurable with a pair of configuration
      variables.
      
      Since we don't need this configured on a per-repository basis, we
      can set it as a global setting.
      
      Closes https://gitlab.com/gitlab-org/gitaly/issues/1747
      d8b2ed54
  20. Jun 05, 2019
  21. May 29, 2019
  22. May 26, 2019
  23. May 24, 2019
  24. May 21, 2019
  25. May 13, 2019
  26. May 12, 2019
  27. May 11, 2019
  28. May 01, 2019
  29. Apr 18, 2019
  30. Apr 16, 2019
Loading