maria-discuss team mailing list archive

[Rich Prohaska <prohaska7@xxxxxxxxx>]

Mariadb should understand the comparison between Myrocks and Tokudb, and
let their current users decide what should be in the product.   It is their
product and their responsibility.  Unfortunately, I am no longer working on
database software as my primary focus, so I can not make any significant
changes to the Tokudb software; it is what it is.

On Wed, Oct 12, 2016 at 6:32 PM, MARK CALLAGHAN <mdcallag@xxxxxxxxx> wrote:

> And if I sound annoyed when talking about TokuDB performance, I am a bit.
> I wish someone else documented the performance problems it has. The
> problems are known but not much has been shared to explain them.  That has
> been left to me as I am promoting the other write-optimized storage engine
> for MySQL. A lot of extremely talented people worked on TokuDB. A few
> (hello Rich) continue to help with it. One of them is related to me (hello
> Tim). One of them works for my employer (Zardosht). I wish more of them
> worked for my employer (anon, anon, anon). Now I get to be the jerk.
>
> On Wed, Oct 12, 2016 at 2:51 PM, MARK CALLAGHAN <mdcallag@xxxxxxxxx>
> wrote:
>
>> If your workload is insert-only and you are happy with TokuDB then please
>> don't try to migrate. But most workloads have reads concurrent with writes.
>> Add that to insert benchmark and TokuDB becomes unhappy. Why do we always
>> get results for insert-only iibench but not for insert+query iibench? My
>> client supports it - https://github.com/mdcallag/
>> mytools/blob/master/bench/ibench/iibench.py
>>
>> I think insert-only iibench is a silly workload with results that are
>> usually taken out of context. MyRocks is great on it, with and without
>> concurrent queries. So I guess I am happy about that.
>>
>> On Wed, Oct 12, 2016 at 12:07 PM, Reinis Rozitis <r@xxxxxxx> wrote:
>>
>>> > I am not surprised that there are so few performance results published
>>> for TokuDB. And when they are published they are almost always for trivial
>>> workloads -- like insert-only insert benchmark. Try adding queries
>>> concurrent with the inserts.
>>>
>>> True but one can see also in your own comment (
>>> https://github.com/facebook/mysql-5.6/issues/25#issuecomment-218494710
>>> ) that some tests in different circumstances can have rather skewed results
>>> which people base their decisions on.
>>>
>>> Glad it has been fixed (would be nice to see some current bench tests).
>>>
>>> rr
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>> --
>> Mark Callaghan
>> mdcallag@xxxxxxxxx
>>
>
>
>
> --
> Mark Callaghan
> mdcallag@xxxxxxxxx
>
> _______________________________________________
> 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
>
>