git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'fawaz ahmed0'" <fawazahmed0@hotmail.com>, <git@vger.kernel.org>
Subject: RE: Reducing Git Repository size - git-filter-repo doesn't help
Date: Sun, 8 Jan 2023 21:36:02 -0500	[thread overview]
Message-ID: <017d01d923d3$20b90bd0$622b2370$@nexbridge.com> (raw)
In-Reply-To: <PH7PR12MB779560B6C003FEE76E4F2471F1FE9@PH7PR12MB7795.namprd12.prod.outlook.com>

On January 8, 2023 9:22 PM, fawaz ahmed0 wrote:
>I have this huge repo: https://github.com/fawazahmed0/currency-api#readme
>and I am trying to reduce its size.
>
>I have run filter-repo script on this repo (
>https://github.com/fawazahmed0/currency-
>api/blob/1/.github/workflows/cleanup-repo.yml ) The commits were reduced
>from 1k to 600 , but the space used is still same. (i.e size-pack: 6.47 GiB
,
>https://github.com/fawazahmed95/currency-
>api/actions/runs/3865919157/jobs/6589710845#step:5:1498 )
>
>Almost all commits of this repo were applied on partially cloned
repository: (
>https://github.com/fawazahmed0/currency-
>api/blob/1/.github/workflows/run.yml ) So I guess it had never run any git
>maintenance task in it's life.
>
>I am not sure what needs to be done to reduce it's space utilization. (
>https://docs.github.com/en/repositories/working-with-files/managing-large-
>files/about-large-files-on-
>github#:~:text=less%20than%205%20GB%20is%20strongly%20recommended )

The first thing you can try is 'git gc --aggressive' to reduce the clone
size. Github automatically does garbage collection. If this is a question of
the size of the working index, look at the sparse-checkout command.

--Randall


  reply	other threads:[~2023-01-09  2:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  2:22 Reducing Git Repository size - git-filter-repo doesn't help fawaz ahmed0
2023-01-09  2:36 ` rsbecker [this message]
2023-01-09  3:29   ` fawaz ahmed0
2023-01-09 10:22 ` Erik Cervin Edin
2023-01-10  2:42 ` Elijah Newren
2023-01-10  8:18   ` fawaz ahmed0
2023-01-11  2:18     ` Elijah Newren
2023-01-11  8:41       ` Elijah Newren
2023-01-11 20:08       ` fawaz ahmed0
2023-01-12  1:54         ` fawaz ahmed0
2023-01-12  2:01           ` Elijah Newren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='017d01d923d3$20b90bd0$622b2370$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=fawazahmed0@hotmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).