admin管理员组

文章数量:1125882

We have a single repository where multiple developers contribute aggressively. This repository is also the source for multiple deployments to Salesforce.

As the repository has grown significantly, we are now experiencing delays in both build and deployment processes due to its large size.

Steps Taken:

  • I cleaned up unused branches, hoping to resolve the issue, but the delays persist.

Suspected Issue:
I believe the problem might be related to the commit history. I am exploring options to clean up the history to reduce the repository's size and improve performance.

Question:

  1. What is the best approach to clean the commit history?
  2. Will clearing the commit history help reduce the repository size and resolve performance issues?
  3. Is there a better alternative approach to this issue?

Any guidance or alternative solutions would be greatly appreciated!

We have a single repository where multiple developers contribute aggressively. This repository is also the source for multiple deployments to Salesforce.

As the repository has grown significantly, we are now experiencing delays in both build and deployment processes due to its large size.

Steps Taken:

  • I cleaned up unused branches, hoping to resolve the issue, but the delays persist.

Suspected Issue:
I believe the problem might be related to the commit history. I am exploring options to clean up the history to reduce the repository's size and improve performance.

Question:

  1. What is the best approach to clean the commit history?
  2. Will clearing the commit history help reduce the repository size and resolve performance issues?
  3. Is there a better alternative approach to this issue?

Any guidance or alternative solutions would be greatly appreciated!

Share Improve this question asked 2 days ago KenruthKenruth 11 bronze badge 1
  • History size should not be that much of a problem for frequent incremental fetches. But if you clone the whole repo frequently, it is a problem. – j6t Commented 2 days ago
Add a comment  | 

1 Answer 1

Reset to default 1

Do you have any binary files (non-text files) in your repository such as PNGs, PDFs, etc. that are changing over time? If they are not on Git-LFS, it could greatly influence the performance of Git. At least, that was the case for us.

本文标签: