WPvivid Backup VS git-sizer

• Comprehensive Backup Options
  WPvivid Backup offers a variety of backup options including full site, database, and file backups, allowing users to customize their backup solutions based on specific needs.
• Ease of Use
  The user interface is intuitive and user-friendly, making it accessible even for those who are not technically inclined.
• Schedule Backups
  Users can schedule backups to run automatically at specified intervals, ensuring regular data protection without manual intervention.
• Migration Functionality
  The plugin facilitates easy migration of websites between domains or hosts, simplifying the process of moving a website.
• Remote Storage Support
  WPvivid supports backup storage in various remote locations like Google Drive, Dropbox, and Amazon S3, providing flexibility and additional security.

Possible disadvantages

• Limited Free Version
  The free version of WPvivid Backup is limited in features, potentially requiring users to upgrade to the pro version for full functionality.
• Resource Intensive
  Backup processes can be resource-intensive, potentially slowing down the website if not configured properly.
• Learning Curve for Beginners
  Despite its intuitive design, beginners might face a learning curve when adjusting specific settings for optimal use.
• Support Response Time
  Some users have reported slower support response times, which can be critical when dealing with urgent backup or restoration issues.

• 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.

No analysis of WPvivid Backup yet.

Tracking WPvivid Backup since May 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