Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4965

Disable auto.gc for large repositories

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Git Hosting
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      As a follow up to STASH-4963 we should consider turning off Git auto gc for large (for some tbd definition of large) repositories.

      Auto GC may be triggered at any time and can take a considerable amount of time for large repositories during which users don't get a hint as to what is going on.

      STASH-4963 demonstrates one example where GC is happening during a push.

      For forks we already turn off auto gc and do the garbage collection in the background. While this shouldn't be the default for all repositories (auto gc has the advantage of happening when necessary without any scheduling concern from our end) it could be beneficial for teams with large repositories as it would avoid opaque pauses.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ssaasen Stefan Saasen (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: