I was testing MariaDB 5.3.1-beta (on Debian 5.0), and bumped into the following weird behavior of user_statistics.busy_time: the value of this column seems completely unreliable and randomly increases at some points in time:
MariaDB [(none)]> SELECT CONNECTED_TIME,BUSY_TIME,CPU_TIME FROM information_schema.user_statistics WHERE USER='core_d7'; +----------------+------------------+------------------+ | CONNECTED_TIME | BUSY_TIME | CPU_TIME | +----------------+------------------+------------------+ | 2887 | 36893488147880.9 | 237.741877899973 |
later...
| 2919 | 36893488147887.3 | 241.586389299972 |
| 2921 | 36893488147888.2 | 242.004482199972 |
and now:
| 3144 | 55340232221635 | 268.829147599973 |
I don't have any additional information information at this point, just wanted to report the behavior in case it rings a bell for someone.
I was testing MariaDB 5.3.1-beta (on Debian 5.0), and bumped into the following weird behavior of user_statistics .busy_time: the value of this column seems completely unreliable and randomly increases at some points in time:
MariaDB [(none)]> SELECT CONNECTED_ TIME,BUSY_ TIME,CPU_ TIME FROM information_ schema. user_statistics WHERE USER='core_d7'; ------- ---+--- ------- ------- -+----- ------- ------+ ------- ---+--- ------- ------- -+----- ------- ------+
+------
| CONNECTED_TIME | BUSY_TIME | CPU_TIME |
+------
| 2887 | 36893488147880.9 | 237.741877899973 |
later...
| 2919 | 36893488147887.3 | 241.586389299972 |
later...
| 2921 | 36893488147888.2 | 242.004482199972 |
and now:
| 3144 | 55340232221635 | 268.829147599973 |
I don't have any additional information information at this point, just wanted to report the behavior in case it rings a bell for someone.