Visual South VS git-sizer

• Industry Expertise
  Visual South specializes in ERP solutions for manufacturing, making them highly knowledgeable in industry-specific requirements and challenges.
• Comprehensive Services
  They offer a full range of services including implementation, training, and support, which helps companies fully leverage their ERP systems.
• Customizable Solutions
  Visual South provides tailored ERP solutions that can be customized to the specific needs of a business, improving operational efficiency.
• Partnership with Infor
  The company is a certified partner of Infor, a leading provider of business cloud software, ensuring access to robust and reliable ERP systems.
• Proven Track Record
  They have a history of successfully implementing ERP solutions for numerous clients, which adds to their credibility and reliability.

Possible disadvantages

• Cost
  Their services and ERP solutions can be expensive, which may be a barrier for small to mid-sized businesses with limited budgets.
• Complexity
  ERP systems can be complex to implement and manage, requiring a significant investment in time and resources from the client.
• Limited to Infor Products
  Their offerings are closely tied to Infor products, which might not be suitable for businesses looking for alternative ERP solutions.
• Geographic Limitations
  The company primarily serves clients in the United States, potentially limiting access for international businesses.
• Long Implementation Time
  Due to the customized nature of their solutions, implementation can take a considerable amount of time, causing delays in realizing ROI.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

Tracking Visual South since Mar 2021.

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago