[MDEV-5774] Enable numa interleaving by default when required conditions are met Created: 2014-03-03  Updated: 2019-07-11

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Jean Weisbuch Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: mysqld_safe, numa

Issue Links:
Relates
relates to MDEV-10829 Enable Innodb NUMA interleave - (and ... Closed
relates to MDEV-12213 NUMA support Open
relates to MDEV-5507 Add the possibility set default param... Closed

 Description   

It would be a good thing to have numa-interleave enabled "automatically" if these conditions are met :

  • The server is running with more than one physical CPU on a NUMA architecture without NUMA interleaving enabled on bios
  • The server is running on Linux
  • The numactl tool is present on the system
  • innodb-buffer-pool-size > memory/physicalCPUcount
    (the latter could be optional)

In that case, there would be parameters for --numa-interleave such as true|false|auto to keep it simple if one want to force it either way.

On another hand, throwing a warning in case the interleaving wouldnt be activated but (innodb-buffer-pool-size > memory/physicalCPUcount) and innodb_buffer_pool_instances wouldnt be set (with a value of 1) could be a good thing.



 Comments   
Comment by Daniel Black [ 2016-12-01 ]

Interleaving is a horrible hack. Though it does have some benefits for providing consistency of response time I think a proper NUMA aware MariaDB is required before we consider enabling it by default.

Comment by brianr [ 2019-07-11 ]

Inquiring: How close are we to having a NUMA aware MariaDB (preferably 10.2) on centos7?

Generated at Thu Feb 08 07:06:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.