percona-discussion team mailing list archive

[Yasufumi Kinoshita <yasufumi.kinoshita@xxxxxxxxxxx>]

If some "singularity" exist at each CPU_TIME measurement, we should
remove them. I will add the singularity treatment code.

But if the problems remain, it may not be MySQL's problem but OS/HW
problem.

-- 
CPU time in user_statistics can be wrong
https://bugs.launchpad.net/bugs/317386
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona patches.

Status in Patches for MySQL by Percona: Confirmed

Bug description:
mysql> select version();
+---------------------------------+
| version()                       |
+---------------------------------+
| 5.0.67-percona-highperf-b10-log |
+---------------------------------+
1 row in set (0.00 sec)

Note CPU time is much more than busy time or connected time. 

  *************************** 2. row ***************************
                  USER: root
     TOTAL_CONNECTIONS: 555184
CONCURRENT_CONNECTIONS: 0
        CONNECTED_TIME: 1763404
             BUSY_TIME: 1112911
              CPU_TIME: 12705452455
        BYTES_RECEIVED: 122864416214
            BYTES_SENT: 653195360443
  BINLOG_BYTES_WRITTEN: 9152373708
          ROWS_FETCHED: 5286277276
          ROWS_UPDATED: 17340086
       TABLE_ROWS_READ: 282889962200
       SELECT_COMMANDS: 84861299
       UPDATE_COMMANDS: 22276439
        OTHER_COMMANDS: 27684991
   COMMIT_TRANSACTIONS: 5008253
 ROLLBACK_TRANSACTIONS: 3396
    DENIED_CONNECTIONS: 3
      LOST_CONNECTIONS: 112
         ACCESS_DENIED: 3
         EMPTY_QUERIES: 15072807