Hello all,
I am encouraged to see this. I thought I would pass this along from
our testing. Near the end of releasing TokuDB v7, we tested 3.1.0,
3.2.0, 3.3.0, and 3.3.1. Performance and stability was the same on
all for tokudb.
So jemalloc 3.1 sounds fine for us.
-Zardosht
On Wed, Apr 24, 201
Hi Sanja,
Oleksandr Byelkin wrote:
> 24.04.2013 19:00, Axel Schwenke пишет:
> [skip]
>>
>> OLTP ro transactions per second relative to glibc malloc
>> --
>> Threadsjemalloc-3.3.1glibc malloctcmallocjemalloc-3.1.0
>
Hi,
Monty asked me to do a quick check how MariaDB performs with jemalloc. This
is in the light of the upcoming integration of TokuDB into the MariaDB tree.
TokuDB requires jemalloc.
While I did use tcmalloc in the connect speed benchmarks with good results,
I did no use jemalloc before. This art
3 matches
Mail list logo