inputprobe DPI Test VS git-sizer

• Measures, does not guess
  A browser cannot ask a mouse for its DPI, so this measures it: you drag the mouse along a reference object of known size and it counts the movement the mouse actually reports over that distance.
• Standard physical references
  Measure against a bank card, whose long edge is 85.60 mm by ISO/IEC 7810, or A4 or US Letter paper at 297 mm and 279.4 mm. The reference is an international standard, so no ruler is involved.
• Three passes, median and spread
  You get the median of three passes plus the spread between them. Passes landing within a percent or two mean the measurement was repeatable; a wide spread means something interfered, and the tool says so.
• Refuses rather than guesses
  When the three passes disagree, no DPI figure is reported. An honest refusal is more useful than a confident wrong number, and the page explains what to change before trying again.
• Free, local, nothing uploaded
  Free and runs entirely in your browser. No account, no signup, no install, and nothing about the measurement leaves your machine.

• 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 inputprobe DPI Test yet.

Tracking inputprobe DPI Test since Aug 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