Hi!

Regarding the TokuDB bugs, they are so far fixed quite quickly by Percona. For example https://bugs.launchpad.net/percona-server/+bug/1607300 was investigated and fixed in less than 10 days, and George answered the same day of the bug report.


And hopefully, the latest remaining patch from Rich needed to enable optimistic parallel replication will be merged quickly as well ( https://github.com/percona/PerconaFT/pull/360 ). The same is true for the RFR patchs on the MariaDB side, ( https://github.com/MariaDB/server/pull/213 + https://github.com/percona/percona-server/pull/1070 ) and the tokubackup script ( https://jira.mariadb.org/browse/MDEV-8843 ) ;)

As for the performance of TokuDB with concurrent read/write queries, from my experience it depends if you try to read immediately the rows which have just been inserted/updated or not. Is this case the messages in the fractal tree have to be propagated and you loose the TokuDB speed insert/update advantage, but they are still a few workload where TokuDB is performing quite well.


Jocelyn Fournier
Founder
M : +33 6 51 21 54 10
https://www.softizy.com
Softizy - At your side to Optimize your PHP / MySQL applications

Le 14/10/2016 à 09:11, Sergei Golubchik a écrit :
Hi, MARK!

On Oct 13, MARK CALLAGHAN wrote:
On Thu, Oct 13, 2016 at 4:00 PM, Sergei Golubchik <s...@mariadb.org> wrote:
There is development and support for TokuDB. The main reason for
dropping it could be RocksDB based engine covering all TokuDB use
cases, but better. I mean, *if* RocksDB will be able to do that,
then TokuDB won't be needed (it's *if*, not a certainty).
Is MariaDB.com providing the development for TokuDB or are you
speculating about the commitment to it provided by someone else? If
the latter, then it would be better to hear directly from them. If the
former, can you be more specific about what MariaDB.com plans to do
for TokuDB?
I am speculating about the commitment to it provided by Percona.
Based on what (I believe) Peter said, and it's in the Colin email too:

Peter says that bugs are fixed for customers... and there is ongoing
development to make it better
but mainly based on the changes I see in TokuDB codebase inside
Percona Server:

5.6.32-78.1 -  73 files changed,  4192 insertions(+), 3715 deletions(-)
5.6.31-77.0 -  35 files changed,   153 insertions(+),   79 deletions(-)
5.6.30-76.3 -  77 files changed,   862 insertions(+),  309 deletions(-)
5.6.29-76.2 -  25 files changed,   487 insertions(+),  153 deletions(-)
5.6.28-76.1 -  14 files changed,   997 insertions(+),  182 deletions(-)
5.6.27-76.0 - 206 files changed, 15619 insertions(+), 5969 deletions(-)
5.6.26-74.0 - initial checkin (into mergetrees/tree/merge-tokudb-5.6 repo)

I agree that it doesn't prove that they will continue to do so in the
future.

If MariaDB.com has any plans about TokuDB - I don't know about them.

Regards,
Sergei
Chief Architect MariaDB
and secur...@mariadb.org

_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to     : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to     : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to