[MDEV-11373] AliSQL: [Perf] Issue#10 BUILD JEMALLOC STATICALLY INTO MYSQLD Created: 2016-11-29  Updated: 2016-11-29  Resolved: 2016-11-29

Status: Closed
Project: MariaDB Server
Component/s: Compiling
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Lixun Peng
Resolution: Won't Do Votes: 0
Labels: None

Epic Link: AliSQL patches

 Description   

Port CMake scripts from mariadb revno:4025,
jemalloc version is the latest stable 4.2.1,
jemalloc website: http://www.canonware.com/jemalloc/
 
Use the jemalloc memory allocator to replace the default
pkmalloc(in glibc), so mysqld can have higher performance for
multiple threads. The corresponding overhead is some more physical
memory(RES) usage.
 
Also add malloc library info, there are two ways to see this info:
  1. `mysqld --version` will show malloc library
  2. mysqld startup info in the error log
and for now, cause we build jemalloc's source code statically, you will
see the malloc library as *bundled jemalloc*.
 
After the introducing of jemalloc, if you run MTR with valgrind
option, you will see a lot of annoying message like
'... are still reachable in loss record ...' from
initialize_performance_schema(). You can safely ignore this, maybe
in the future, we will find a way to fix this issue.

https://github.com/alibaba/AliSQL/commit/5d84f891406793100a2e5a26d2e4692db64e9c46



 Comments   
Comment by Sergey Vojtovich [ 2016-11-29 ]

plinux, this patch was originally taken from MariaDB. While we still support jemalloc, we don't bundle it anymore. Also we expose memory allocation library via version-malloc-library system variable.

Said the above, is there still anything you'd like us to take from this patch?

Comment by Lixun Peng [ 2016-11-29 ]

svoj I think we needn't to do anything about this patch since this patch was taken from MariaDB.

Comment by Sergey Vojtovich [ 2016-11-29 ]

Closing per plinux comment.

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