Live data from Hacker News

Viewing profile — zardosht

zardosht

HN member
Joined
Thu, Jan 10, 2013, 8:59 PM UTC
HN karma
91
Public activity
25 items

About zardosht

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #7992451

    Another thing to keep in mind is that not all systems are meant to be CP systems.

  3. comment
    Comment #7990897

    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…

  4. comment
    Comment #7990823

    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 i…

  5. comment
    Comment #7554111

    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 (w…

  6. comment
    Comment #7553888

    TokuMX does have MVCC

  7. comment
    Comment #7553826

    TokuMX, which I work on, has document level locking and compression right now.

  8. comment
    Comment #7236419

    (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…

  9. comment
    Comment #7233901

    ddorian, Can you elaborate what that means?

  10. story
  11. comment
    Comment #7220433

    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. Neverthe…

  12. story
  13. comment
    Comment #6098194

    MongoDB 2.2 and 2.4

  14. story
  15. comment
    Comment #5909739

    Just as in our TokuDB for MySQL product, we have zlib and lzma compression available.

  16. comment
  17. comment
    Comment #5909393

    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…

  18. comment
    Comment #5909236

    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 ye…

  19. comment
    Comment #5826307

    From Leif earlier, "TokuMX offers multi-document transactional semantics without application changes (snapshot reads), as well as protocol support for multi-statement (read-modify-…

  20. comment
    Comment #5825819

    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 M…

  21. comment
    Comment #5825304

    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 applicatio…

  22. comment
    Comment #5590370

    Hope this helps, from Tokutek's website: http://www.tokutek.com/solutions/

  23. comment
    Comment #5590296

    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, T…

  24. comment
    Comment #5589641

    Link to source code: https://github.com/tokutek

  25. comment
    Comment #5589578

    And our google groups: - tokudb-dev - tokudb-user