maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #01022
Re: Benchmark with jemalloc
hum.... i'm a bit confused now.... reading the revision patch..
http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/3888#extra/jemalloc/VERSION
3.3.1-0-g9ef9d9e8c271cdf14f664b871a8f98c827714784
why 3.3.1 if 3.1.0 should be better?
2013/9/18 Roberto Spadim <roberto@xxxxxxxxxxxxx>
> hum... that's a point to consider, the last link (
> https://lists.launchpad.net/maria-developers/msg05425.html) is a bit old:
> Date: Wed, 24 Apr 2013 18:00:51 +0200
>
> maybe time to a new benchmark? or better explain about binary packages of
> mariadb? i use the source code version some times and didn't remember about
> checking malloc versions
>
> from changelog:
>
> - Revision #3888<http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/3888>
> [merge] Tue 2013-09-10 23:02:25 +0200
> - merge with 5.5-tokudb tree (TokuDB 7.0.4). In particular:
> - add TokuDB, together with the ft-index library
> - cmake support, auto-detecting whether tokudb can be built
> - fix packaging - tokudb-engine.rpm, deb
> - remove PBXT
> - add jemalloc (no information about version here)
> - the server is built with jemalloc by default even if TokuDB is
> not built (no information about version here)
> - documentation files in RPM are installed in the correct
> location
> - support for optional deb packages (tokudb has specific build
> requirements)
> - move plugins from mariadb-server deb to appropriate debs
> (server/test/libmariadbclient)
> - correct mariadb-test.deb to be not architecture-independent
> - fix out-of-tree builds to never modify in-tree files
> - new handler::prepare_index_scan() method
>
>
>
>
>
>
>
>
>
> 2013/9/18 Reindl Harald <h.reindl@xxxxxxxxxxxxx>
>
>> well, recent is 3.4.0
>> however, the releas enotes are not really true
>> jemalloc not linked nor loaded
>>
>> https://mariadb.com/kb/en/mariadb-5533-release-notes/
>> Other Notable Information
>> MariaDB is now built with jemalloc by default on Linux
>>
>> [root@testserver:~]$ rpm -q --file /usr/libexec/mysqld
>> mariadb-server-5.5.33-6.fc19.20130917.rh.x86_64
>>
>> [root@testserver:~]$ ldd /usr/libexec/mysqld
>> linux-vdso.so.1 => (0x00007fff16c89000)
>> libaio.so.1 => /lib64/libaio.so.1 (0x00007f8af9864000)
>> libz.so.1 => /lib64/libz.so.1 (0x00007f8af964c000)
>> libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f8af9414000)
>> libdl.so.2 => /lib64/libdl.so.2 (0x00007f8af9210000)
>> libssl.so.10 => /lib64/libssl.so.10 (0x00007f8af8fa8000)
>> libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f8af8bd6000)
>> libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f8af88d2000)
>> libm.so.6 => /lib64/libm.so.6 (0x00007f8af85d0000)
>> libgomp.so.1 => /lib64/libgomp.so.1 (0x00007f8af83c0000)
>> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f8af81a4000)
>> libc.so.6 => /lib64/libc.so.6 (0x00007f8af7de3000)
>> /lib64/ld-linux-x86-64.so.2 (0x00007f8afb1f5000)
>> libfreebl3.so => /lib64/libfreebl3.so (0x00007f8af7b76000)
>> libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2
>> (0x00007f8af792d000)
>> libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f8af764f000)
>> libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f8af744a000)
>> libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f8af7215000)
>> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f8af6fff000)
>> libkrb5support.so.0 => /lib64/libkrb5support.so.0
>> (0x00007f8af6df0000)
>> libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f8af6bec000)
>> libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f8af69d2000)
>> libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f8af67ae000)
>> libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f8af654a000)
>>
>> [root@testserver:~]$ rpm -qa | grep jemalloc
>> jemalloc-devel-3.4.0-1.fc19.x86_64
>> jemalloc-3.4.0-1.fc19.x86_64
>>
>> [root@testserver:~]$ lsof | grep jemalloc
>> [root@testserver:~]$
>>
>> Am 18.09.2013 17:54, schrieb Roberto Spadim:
>> > hummm maybe at mariadb-5.5 release notes should explain about using
>> > jemalloc-3.1.0 ? instead of 3.3.1? from what i read, this give a big
>> > difference in server with many cores
>> >
>> > 2013/9/18 Reindl Harald <h.reindl@xxxxxxxxxxxxx>:
>> >>
>> >>
>> >> Am 18.09.2013 17:40, schrieb Roberto Spadim:
>> >>> Hi guys, there're benchmark with jemalloc and last malloc
>> implemention?
>> >>
>> >> the much more interesting question - how to build MariaDB with jemalloc
>> >>
>> >> https://lists.launchpad.net/maria-developers/msg05425.html
>> >> does not really give an answer
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~maria-discuss
>> Post to : maria-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maria-discuss
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Roberto Spadim
> SPAEmpresarial
>
--
Roberto Spadim
SPAEmpresarial
References