A top-like real-time monitoring tool for MySQL that visualizes server load using performance_schema data.
ps-top is a command-line monitoring tool for MySQL 5.6+ that collects and displays real-time server performance data from the performance_schema database. It helps database administrators quickly identify bottlenecks, analyze table and file I/O patterns, and monitor user activity.
Database administrators and DevOps engineers managing MySQL 5.6+ or MariaDB servers who need real-time performance monitoring and bottleneck analysis.
Developers choose ps-top for its focused, real-time visualization of performance_schema data with interactive navigation across seven detailed views, offering a standardized alternative to server-specific tools for identifying optimization opportunities.
ps-top - a top-like program for MySQL
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Shows detailed latency and operation counts per table, split by select, insert, update, and delete activity, enabling precise bottleneck identification as described in the Table I/O Analysis feature.
Offers seven different data views with keyboard shortcuts for navigation and adjustable polling intervals, allowing dynamic performance monitoring without interrupting workflow.
Supports multiple MySQL connection methods, including defaults files, command-line parameters, and environment variables like MYSQL_DSN, with options for TLS and parameter interpolation to reduce latency.
Tracks connected users, their hosts, and query latency statistics, helping identify active users and potential bottlenecks, though limited by MySQL's resolution for short queries.
Requires performance_schema to be enabled, which is disabled by default in MariaDB >=10.0.12, necessitating server configuration changes and a restart, adding setup complexity.
The user latency view suffers from low resolution due to MySQL bug #75156, making it less effective for monitoring very short queries, as admitted in the README.
Views like mutex_latency and stages_latency may be empty without proper grants to modify setup_instruments, and restoring settings on exit adds administrative overhead.
Installation depends on Go, and compatibility issues may arise with older versions, as noted in the README, potentially hindering adoption in environments without Go or with outdated versions.