…_STATISTICS, which shows statistics per client’s hostname, not per user FLUSH USER_ and CLIENT_STATISTICS commands Our port includes: INFORMATION_SCHEMA tables – USER_STATISTICS, CLIENT_STATISTICS, INDEX_STATISTICS, TABLE_STATISTICS Access protection – USER_STATISTICS, CLIENT_STATISTICS available only for user with SUPER or PROCESS privileges. INDEX_STATISTICS, TABLE_STATISTICS shows only information…
Post: MySQL extensions for hosting
… per-user and per-table accounting to the database, accessible with a new set of commands such as SHOW TABLE_STATISTICS, SHOW INDEX_STATISTICS and SHOW USER_STATISTICS… catch users causing the most traffic to help you with some strategic decisions. Sample outputs: mysql> SHOW USER_STATISTICS LIKE ‘hosting2′\G *************************** 1. row *************************** User…
Post: Userstats patches with information schema support
… information schema tables added: user_statistics, table_statistics, index_statistics. One can now use select * from information_schema.user_statistics along with show user_statistics. Links: Patch for 5…
Comment: MySQL extensions for hosting
… statistics). I may be biased, but I could not do without this feature. It makes it very easy to determine which users… over time. Once a load problem is isolated to one user, statement sampling can be used to determine the statements that… a column for IO per user to SHOW USER_STATISTICS. I think that the patch left out FLUSH TABLE_STATISTICS, but that will be in…
Comment: Percona builds with Percona patchsets
Mark, Yes, it contains SHOW USER_STATISTICS / INDEX_STATISTICS / TABLE_STATISTICS. We are going to make this info available via INFORMATION_SCHEMA.
Comment: Managing Slave Lag with MySQL Replication
If we can get the ‘SHOW USER_STATISTICS‘ functionality from the Google patch into MySQL, then you can … for the system user and Uptime as reported by SHOW STATUS. Busy_time is the number of seconds that user had been running…
Comment: Missing Data - rows used to generate result set
For the upcoming Google patch SHOW USER_STATISTICS includes CPU time, bytes sent, bytes received, binlog bytes written and rows read per account. Alas, we have yet to add disk reads/writes per user — they are not as easy to count.
Comment: Percona builds with Percona patchsets
This is excellent news and great for users who want performance critical features but don’t want to patch and build MySQL. SHOW USER_STATISTICS is my favorite patch so far, does this include it?
Post: The perils of InnoDB with Debian and startup scripts
… | user | statistics | select … | 6344 | user | | NULL | 6345 | user | Updating | update … | 6346 | user | Sorting result | insert … | 6351 | user | | NULL | 6355 | user | | NULL | 6356 | user | statistics | select … | 6357 | user | statistics | select … | 6358 | user | Sending… … | 6359 | user | statistics | select … | 6360 | user | | NULL | 6361 | user | | NULL +——+——————+—————-+————- Notice all those processes in ‘statistics‘ status. Why is that happening? Look at SHOW INNODB STATUS…
Post: MySQL Binaries Percona build10
… potential logging and statistics overhead, so now you can fully turn on / off query statistics for microslow patch and user statistics in runtime. Next… are Innodb_scan_* | | userstatsv2.patch | SHOW USER/TABLE/INDEX statistics | V2 | Google | GPL | Added INFORMATION_SCHEMA.*_STATISTICS | | show_patches.patch | SHOW PATCHES | 1.0 | Jeremy Cole…

