Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.1.6, 10.2.0, 10.3.0, 10.4.0, 10.5.0
-
Component/s: Galera
-
Labels:None
-
Epic Link:
Description
Data comes from Sandy Bridge system running sysbench OLTP RO in 1 thread against 1 table.
Call graphs:
- 0.14% mysqld mysqld
|
- wsrep_on
|
+ 28.85% ha_innobase::general_fetch(unsigned char*, unsigned int, unsigned int)
|
+ 26.34% handler::ha_index_next(unsigned char*)
|
+ 19.48% handler::index_read_idx_map(unsigned char*, unsigned int, unsigned char const*, unsigned long, ha_rkey_function)
|
+ 13.60% ha_innobase::index_read(unsigned char*, unsigned char const*, unsigned int, ha_rkey_function)
|
+ 9.40% handler::ha_index_read_map(unsigned char*, unsigned char const*, unsigned long, ha_rkey_function)
|
+ 2.15% innobase_commit(handlerton*, THD*, bool)
|
wsrep_on() is the one defined in wsrep_mysqld.cc. Most time spent for function call convention. I guess all calls come from InnoDB. Either call WSREP() or cache wsrep_on() value.
Attachments
Issue Links
- causes
-
MDEV-22452 Missing call to wsrep_commit_ordered in trx_t::commit
-
- Closed
-
- relates to
-
MDEV-22203 WSREP_ON is unnecessarily expensive to evaluate
-
- Closed
-