Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-5288

Provide basic NUMA support for both InnoDB and TokuDB

    Details

    • Type: Improvement
    • Status: On Hold
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Packaging
    • Labels:
      None

      Description

      With InnoDB NUMA support in source code, it sets NUMA policy to default at the end of buffer pool allocation. It is not clear whether that default means global system default (local node allocation), or numactl-set policy if any.

      We would like to have TokuDB use interleaved NUMA policy. But if InnoDB resets policy to global system default, this will not work, regardless if one used numactl.

      Thus

      • check if numactl with fixed InnoDB NUMA support (5.7.12-5) results in TokuDB using interleaved allocations or not
      • if it does, add numactl back to mysqld_safe
      • if it does not, choose one of the fix options: 1)) removing NUMA support from InnoDB, leaving only numactl; 2) adding NUMA support to TokuDB source, avoiding numactl

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                evgeniy.patlan Evgeniy Patlan
                Reporter:
                laurynas.biveinis Laurynas Biveinis (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: