RunWisp VS git-sizer

• Cron scheduling
  Run jobs on a schedule with cron expressions. A complete crond replacement, with second-level precision.
• Process supervision
  Keep long-running services alive and restart them automatically on crash - a supervisord replacement in the same binary.
• Per-run history
  Every run recorded with its exit code, duration, and captured output, browsable at any time. Nothing is silently lost.
• Failed & missed-run alerts
  Get notified when a job fails or when a scheduled run never fires at all.
• Built-in Web UI
  See every job, run, and log line in a clean browser UI, and trigger tasks - no SSH login to the server required.
• Terminal UI (TUI)
  A full-screen terminal interface to watch runs live and browse history straight from the shell.
• REST API
  Everything the dashboard does, available over HTTP for automation and integration.
• Lightweight and Fast
  One ~25 MB Go binary. No Python, no Node, no external database to install or maintain.
• Config As Code
  Define every job and service in one readable runwisp.toml you can commit to git and review like any other code.
• Real-time log streaming
  Watch a job's output stream live as it runs, right in the dashboard or TUI.
• Retries with backoff
  Automatically retry failed jobs with configurable backoff, instead of leaving them dead until someone notices.

• 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 RunWisp since Jul 2026.

• 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