Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
We haven't seen any noticeable speed improvements from building the server with jemalloc. And we did have user complains about inability to use other memory allocators with MariaDB. But TokuDB (and, possibly, RockDB) need jemalloc for a good performance.
A solution could be:
- do not build with jemalloc
- add malloc-liib=jemalloc to tokudb.cnf and manually add a jemalloc dependency to TokuDB packages
- something similar should be done for systemd too
- as TokuDB will now introduce an additional dependency that the server itself does not need, it will go into a separate rpm/deb package
This way
- the server will not be built with jemalloc, won't require or run with it
- when a TokuDB package is installed, it will automatically bring in jemalloc as a dependency and will make the server use it — just as before
- the user can always override it and use another memory allocator, if desired
Attachments
Issue Links
- relates to
-
MDEV-18012 Supplied jemalloc results in immediate MariaDB Segfault on aarch64
- Closed