wookayin/gpustat

📊 A simple command-line utility for querying and monitoring GPU status

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 15th, 2026
Created on April 24th, 2016
Open Issues & Pull Requests: 30 (+0)
GitHub issues: Enabled
Number of forks: 285
Total Stargazers: 4,393 (+0)
Total Subscribers: 41 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.9 days
Mean response time: 20.7 days
90th percentile: 50.8 days
Tracked items: 7

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,114 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (3)
  • invalid (1)
  • pynvml (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

gpustat is a command-line utility for querying and monitoring GPU status.

The tool addresses the need for a simpler, more readable alternative to nvidia-smi for checking GPU usage and health. It parses output from nvidia-smi and presents GPU information in a cleaner, more human-friendly format. Users can quickly see which GPUs are available, their memory usage, temperature, and which processes are consuming GPU resources without wading through nvidia-smi's verbose output.

The project suits developers and researchers who frequently need to check GPU availability and utilization from the command line, particularly those working with machine learning, scientific computing, or other GPU-intensive workloads. It is especially useful in shared computing environments where multiple users need to monitor GPU allocation. The tool is lightweight and straightforward, making it a good fit for quick status checks and scripting scenarios where a simpler interface than nvidia-smi is preferred.

Development on the project is active and responsive to user needs. The maintainer regularly merges pull requests that add features and fix issues. The project maintains good test coverage and addresses bug reports promptly. Documentation is kept current and reflects the tool's actual capabilities and usage patterns.