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

QUICK_RANGE_SELECT::get_next() takes 0.17% in OLTP RO

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.1(EOL)
    • 10.2(EOL)
    • None
    • None

    Description

      Data comes from Sandy Bridge system running sysbench OLTP RO in 1 thread against 1 table.

      Call graphs:

      -   0.17%  mysqld  mysqld
      		 
         - QUICK_RANGE_SELECT::get_next()
      		 
            + 36.73% rr_quick(READ_RECORD*)
      		 
            + 29.42% sub_select(JOIN*, st_join_table*, bool)
      		 
            + 22.79% create_sort_index(THD*, JOIN*, st_order*, unsigned long long, unsigned long long, bool)
      		 
            + 11.06% filesort(THD*, TABLE*, st_sort_field*, unsigned int, SQL_SELECT*, unsigned long long, bool, unsigned long long*, unsigned long long*)

      Most time spent for function call convention. A good candidate for inlining?

      Attachments

        Activity

          No workflow transitions have been executed yet.

          People

            psergei Sergei Petrunia
            svoj Sergey Vojtovich
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.