Busy_time rate is a million times higher from 11.4.4 to 11.4.5
Good day When I start a 11.4.4 image and I watch USER_STATISTICS.BUSY_TIME refreshing it every second or so, it increases with about 0.0002 at a time (for a user that's not really doing anything). But when I do the same in a 11.4.5 image it goes up by about 200 at a time (while the user is still not doing anything). I think that's wrong because it's supposed to be "number of seconds of activity". I couldn't find anything about it in the release notes https://mariadb.com/kb/en/mariadb-11-4-5-release-notes/ . Any ideas? I also see this in production and it quite messes up our metrics 😅 Thanks you
Gathering some statistics for all current LTS versions it seems something definitely changed: DO SLEEP(0.5) SELECT BUSY_TIME FROM information_schema.USER_STATISTICS WHERE USER="root" 10.6.0 : 0.501819 10.6.1 : 0.501053 10.6.2 : 0.501648 10.6.3 : 0.501604 10.6.4 : 0.501832 10.6.5 : 0.501544 10.6.7 : 0.501955 10.6.8 : 0.501876 10.6.9 : 0.501897 10.6.10 : 0.501433 10.6.11 : 0.501622 10.6.12 : 0.501835 10.6.13 : 0.501748 10.6.14 : 0.501707 10.6.15 : 0.501714 10.6.16 : 0.501779 10.6.17 : 0.501494 10.6.18 : 0.501867 10.6.19 : 0.502027 10.6.20 : 0.501747 10.6.21 : 0.501988 10.11.2 : 0.501824 10.11.3 : 0.501596 10.11.4 : 0.501717 10.11.5 : 0.501656 10.11.6 : 0.501781 10.11.7 : 0.501928 10.11.8 : 0.502130 10.11.9 : 0.501888 10.11.10 : 0.501705 10.11.11 : 501735.000000 11.4.2 : 0.500968 11.4.3 : 0.501843 11.4.4 : 0.501671 11.4.5 : 501860.000000
Hi, Bas, Thanks. This is a very thorough, it helped me to find the bug quickly. I've reported it as https://jira.mariadb.org/browse/MDEV-36586 will be fixed in the next release. In the future you might consider reporting bugs at jira.mariadb.org yourself, this way you'll be automatically notified when the bug is fixed. Regards, Sergei Chief Architect, MariaDB Server and security@mariadb.org On Apr 08, Bas via discuss wrote:
Gathering some statistics for all current LTS versions it seems something definitely changed:
DO SLEEP(0.5)
SELECT BUSY_TIME FROM information_schema.USER_STATISTICS WHERE USER="root"
10.6.0 : 0.501819 10.6.1 : 0.501053 10.6.2 : 0.501648 10.6.3 : 0.501604 10.6.4 : 0.501832 10.6.5 : 0.501544 10.6.7 : 0.501955 10.6.8 : 0.501876 10.6.9 : 0.501897 10.6.10 : 0.501433 10.6.11 : 0.501622 10.6.12 : 0.501835 10.6.13 : 0.501748 10.6.14 : 0.501707 10.6.15 : 0.501714 10.6.16 : 0.501779 10.6.17 : 0.501494 10.6.18 : 0.501867 10.6.19 : 0.502027 10.6.20 : 0.501747 10.6.21 : 0.501988 10.11.2 : 0.501824 10.11.3 : 0.501596 10.11.4 : 0.501717 10.11.5 : 0.501656 10.11.6 : 0.501781 10.11.7 : 0.501928 10.11.8 : 0.502130 10.11.9 : 0.501888 10.11.10 : 0.501705 10.11.11 : 501735.000000 11.4.2 : 0.500968 11.4.3 : 0.501843 11.4.4 : 0.501671 11.4.5 : 501860.000000
Hi Sergei Thank you for fixing it! I'll use the jira next time if I find another bug (which, in hindsight this obviously was) Thanks, Bas
participants (3)
-
Bas -
mdbml.myself854＠passmail.net
-
Sergei Golubchik