zardosht

16 ms·

1.
Introducing Ark: A Consensus Algorithm For TokuMX and MongoDB(tokutek.com)
37 points by zardosht 12y ago|16 comments
2.
by zardosht 12y ago
Another thing to keep in mind is that not all systems are meant to be CP systems.
3.
by zardosht 12y ago
Your last question is a bit loaded with a bunch of "ifs", so let's unwind it. I don't know what MongoDB will "support" as far as other engines go. But assuming we, Tokutek, release something that we support tha
4.
by zardosht 12y ago
Another engineer at Tokutek here. As you see, we are up to 2.4, and have been investigating 2.6 and Geo. With all possible features, whether they be from MongoDB 2.6 or things we innovate on our own like partitioned collections, we prioriti
5.
by zardosht 12y ago
Not for single-server performance. The database level lock severely limits MongoDB's single server performance. Just look up the sysbench benchmark comparing MongoDB with TokuMX (which I work on)
6.
by zardosht 12y ago
TokuMX does have MVCC
7.
by zardosht 12y ago
TokuMX, which I work on, has document level locking and compression right now.
8.
by zardosht 13y ago
(I work for Tokutek) Write concurrecy: yes, TokuMX does not have a database level reader/writer lock. Index Building: yes, fractal trees can write data much more efficiently, so if index building is a problem, I bet TokuMX solves it. P
9.
by zardosht 13y ago
ddorian, Can you elaborate what that means?
10.
TokuMX 1.4: Major improvements to MongoDB sharding and replication(tokutek.com)
20 points by zardosht 13y ago|19 comments
11.
by zardosht 13y ago
Roger, I work at Tokutek (and wrote the post above). I'm sorry you ran into issues trying out TokuMX. I assure you, we are "ready", as we have users running in production. Nevertheless, you ran into problems and that is unfor
12.
TokuMX vs MongoDB on in-memory sysbench benchmark(tokutek.com)
9 points by zardosht 13y ago|0 comments
13.
by zardosht 13y ago
MongoDB 2.2 and 2.4
14.
Comparing MongoDB, MySQL, and TokuMX Data Layout(tokutek.com)
2 points by zardosht 13y ago|0 comments
15.
by zardosht 13y ago
Just as in our TokuDB for MySQL product, we have zlib and lzma compression available.
16.
by zardosht 13y ago
Staying up to date is not an all-or-none proposition. We use feedback to drive direction. For example, even though we used 2.2 as a base, user feedback compelled us to include hash-based sharding, a 2.4 feature, in this release.
17.
by zardosht 13y ago
I work for Tokutek. Slava, thanks for the kind words. Just to clear up any possible confusion, this is the product. We release and support TokuMX. The research started roughly a year ago (the blog posts we've done are out there), and i
18.
by zardosht 13y ago
From Leif earlier, "TokuMX offers multi-document transactional semantics without application changes (snapshot reads), as well as protocol support for multi-statement (read-modify-write style) transactions, within a single shard. We are sti
19.
by zardosht 13y ago
TokuMX was forked from 2.2.4, but we have and will continue to add features from 2.4. For instance, hash based sharding is in TokuMX. One cannot mix a replica set with TokuMX and MongoDB.
20.
by zardosht 13y ago
I work for Tokutek. In addition to performance improvements and compression, another cool thing about TokuMX: it's fully transactional. We hope this makes development of applications simpler.
21.
by zardosht 13y ago
Hope this helps, from Tokutek's website: http://www.tokutek.com/solutions/
22.
by zardosht 13y ago
One big differentiating feature between TokuDB and other write optimized databases is that TokuDB is fully transactional, it is ACID compliant. There is a demand for this. AFAIK, TokuDB is the only write-optimized transactional data store.
23.
by zardosht 13y ago
Link to source code: https://github.com/tokutek
24.
by zardosht 13y ago
And our google groups: - tokudb-dev - tokudb-user