Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9541

Closed
Open
Created Aug 07, 2015 by Administrator@rootOwner

[Info request] GitLab repo use more space than imported repo

Created by: tsumi

Hi, i noticed that repos created and populated trough gitlab commit-by-commit use more disk space than repos created on gitlab but imported trough remote add/git push from an existing repo.

For example, gitlab managed repo:

  • real data (git clone of all branch): 796Kb
  • on server: 2356Kb (about 3 times)

repo imported into Gitlab:

  • real data (git clone of all branch): 3776Kb
  • on server: 4064Kb (quite the same, some commit was made on gitlab after import)

Is this a sort of bug or an expected behavior (and, in this case, why more space is used?)

Thanks Best Regards :)

Assignee
Assign to
Time tracking