Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7962

wsrep_on() takes 0.14% in OLTP RO

        Details

        • Type: Bug
        • Status: Open
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: 10.1
        • Fix Version/s: 10.1
        • Component/s: Galera
        • Labels:
          None

          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.

            Gliffy Diagrams

              Attachments

                Activity

                There are no comments yet on this issue.

                  People

                  • Assignee:
                    nirbhay_c Nirbhay Choubey
                    Reporter:
                    svoj Sergey Vojtovich
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated: