[MXS-4905] Warn about THP after startup Created: 2023-12-18 Updated: 2023-12-20 Resolved: 2023-12-20 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 6.4.14, 22.08.12, 23.02.9, 23.08.5 |
| Type: | Task | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-198 |
| Description |
|
If THP is enabled, MaxScale should log a warning stating that it might use more memory than is expected. For a future release, once static buffers have been allocated, all runtime buffers could disable use of transparent hugepages. The query classifier cache is expected to take up notable amounts of memory and it should not use THP as it is not optimized for it. Some of the buffers in the query canonicalization code could benefit from it but the benefits of it ought to be first measured. The effects of THP should also be evaluated to estimate if there is any performance benefit to enabling it in general. |
| Comments |
| Comment by markus makela [ 2023-12-19 ] |
|
Added a notice level message to 6.4 that is logged whenever transparent hugepage are set to always. In newer releases this could be made into a warning if a way to disable it is added. |