Re: [Maria-discuss] fsync alternative

2019-09-12 Thread pslawek83
Hi Jure, maybe you can try using toku engine. I noticed that with large keycaches syncing it to disk can sometimes take up to a minute for myisam tables. Also innodb is generally heavy on I/O. Toku on the other hand is heavier on CPU/memory but seems very light on I/O (from my experience), so

Re: [Maria-discuss] Rocks, toku and some performance considerations.

2019-09-12 Thread jocelyn fournier
Hi! It seems MariaDB is dropping TokuDB in 10.5. See https://jira.mariadb.org/browse/MDEV-19780 BR, Jocelyn Fournier > Le 12 sept. 2019 à 14:31, pslawek83 a écrit : > > Hi Everyone, i got recently interested in rocks and have a couple of > questions if anyone else is doing/done some

Re: [Maria-discuss] Rocks, toku and some performance considerations.

2019-09-12 Thread Jonas Krauss
Hello, how did you configure myrocks/rocksdb? Have you set up bloom filters? Maybe you could post your rocksdb options from the my.cnf in use here. This link was helpful to me when setting up myrocks: https://smalldatum.blogspot.com/search?q=myrocks+options Regards Jonas Am Do., 12. Sept.

[Maria-discuss] Rocks, toku and some performance considerations.

2019-09-12 Thread pslawek83
Hi Everyone, i got recently interested in rocks and have a couple of questions if anyone else is doing/done some migrations to this engine: 1. Noticed that compared to toku - I/O overhead for range SELECTs with cold caches is much higher, especially on vmware I/O utilization (WAit) goes over

Re: [Maria-discuss] Json validation of unicode escaped strings

2019-09-12 Thread Sergei Golubchik
Hi, Manoj! This looks like https://jira.mariadb.org/browse/MDEV-19760 which was just fixed recently and should be out in the next release. On Sep 11, manoj wrote: > I am trying to insert json data in to a table with json check > constraint. The non-ascii characters are unicode escaped. > This