Details

    • Type: Epic
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: OTHER
    • Labels:
      None
    • Epic Name:
      Performance: micro optimizations

      Description

      In MariaDB there seem to be no major (>5%) bottlenecks for CPU bound workloads. However there's a whole bunch of more or less easily fixable minor things that waste inexcusable amount of time. Among those:

      • one-line virtual methods that can't be inlined
      • simple functions defined in source file that can't be inlined
      • abuse of likely()/unlikely() (likely in InnoDB, PFS)
      • added (sometimes complex) conditions (PFS, WSREP, PROFILING)
      • frequent calls of pthread_getspecific() (InnoDB, parser, optimizer)

      See linked issues for details.

        Gliffy Diagrams

          Attachments

            Issues in Epic

              Activity

              Hide
              svoj Sergey Vojtovich added a comment -

              Since it was agreed to keep performance schema intact, further analysis will be done with performance schema compiled out.

              Show
              svoj Sergey Vojtovich added a comment - Since it was agreed to keep performance schema intact, further analysis will be done with performance schema compiled out.

                People

                • Assignee:
                  svoj Sergey Vojtovich
                  Reporter:
                  svoj Sergey Vojtovich
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated: