[MDEV-13785] MariaDB 10.2. [7,8] does not use hugepages Created: 2017-09-12 Updated: 2018-05-29 Resolved: 2018-03-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2.7, 10.2.8, 10.2 |
| Fix Version/s: | 10.2.15 |
| Type: | Bug | Priority: | Major |
| Reporter: | Devin Yu | Assignee: | Sergey Vojtovich |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | Hugepages | ||
| Environment: |
CentOS Linux release 7.3.1611 (Core) |
||
| Attachments: |
|
| Description |
|
It seems MariaDB 10.2.[7,8] does not use hugepages, but MariaDB 10.1.x,the same configuration, can use hugepages. Thank you.
|
| Comments |
| Comment by Elena Stepanova [ 2017-10-01 ] |
|
Thanks for the report, I can reproduce it with InnoDB. Seems to work with MyISAM. I think the problem might be caused by the change of the variable used in 10.2 vs 10.1. In 10.1, the logic is under HAVE_LARGE_PAGES, while in 10.2 it's under HAVE_LINUX_LARGE_PAGES. The change came with InnoDB 5.7 merge; but in MySQL 5.7, cmake files were changed accordingly, and the other code also uses the new name, while in 10.2 it's only checked in InnoDB, but isn't set anywhere, and the server still uses HAVE_LARGE_PAGES. |
| Comment by Daniel Black [ 2018-03-22 ] |
|
so pushing `HAVE_LINUX_LARGE_PAGES` to the wider server code is the recommended fix for now? |
| Comment by Marc [ 2018-04-03 ] |
|
Hi, this bug is closed and marked as fjxed in 10.2.14 but is not present in the change log of 10.2.14. Also 10.2.14 was released beginnig of march while the fixed status was set on march 29 and last the pull request is marked as declined ... I installed 10.2.14 and I confirm that hugepages is trill not used by innodb. Could someone clarify the real status of this issue? |
| Comment by Sergey Vojtovich [ 2018-04-03 ] |
|
Sorry, wrong fix version was set. To be released along with 10.2.15. |
| Comment by Marc [ 2018-04-03 ] |
|
thanks |