Bug #48994 Default server stats gathering for MacOSX seems not working correctly

Submitted:	23 Nov 2009 13:30	Modified:	15 Dec 2009 16:38
Reporter:	Geert Vanderkelen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.8	OS:	MacOS (10.6.2)
Assigned to:		CPU Architecture:	Any

Description:
In Workbench Server Administration:

The Server Stats gathering seems a bit broken. CPU is multiplied by 100, and the memory doesn't show at all.

Bit frustrating testing cause of bug #48992

How to repeat:
get_cpu_info = /usr/bin/uptime | wba_token(' ', 10)

14:23  up 3 days, 10:03, 7 users, load averages: 0.98 0.95 0.93

The token is indeed 10th, but in the stats when opening the instance it's showing as 98%, sometimes 104%.
Something is multiplying it by 100?

get_mem_info = vm_stat | wba_filter(free) | wba_token(':', 1)

Pages free:                          32071.
Pages active:                       402715.
Pages inactive:                     274796.
Pages speculative:                  113345.

Filter is OK, token also but the number ends with a '.', not sure if that give problems?
Just mentioning it because the stats don't show anything when you open the instance.

Scale is fixed for osx and linux.

Failing memory stats could not be reproduced on osx 10.6 and osx 10.5.

fixed in repositoy.
will be included in 5.2.11

An entry has been added to the 5.2.11 changelog:

In the Server Status section of the Admin screen, the values for CPU status appeared to be erroneously multiplied by 100, and the Memory status appeared to be continually 0.

Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.