| My other reply didn't address some of your specific questions about 2.8: > We're seeing document-level locking We've had it from the beginning. Their implementation so far doesn't handle index updates or replication. I assume they'll handle these issues before a GA release, but the interesting question is which workloads will still demonstrate good concurrency after they solve these problems. > possible B-Tree improvements (I presume Toku's R-Tree/Fractals [can't remember which they use] will still be superior) I haven't seen any actual improvements they've got planned. Besides, B-trees will never compete with our fractal trees on insertions or compression, or for that matter, with LSM trees either. > possible transactions (although what's on JIRA hasn't convinced me so far) They aren't going to do transactions in 2.8. They may provide something like some transactional semantics we provide in TokuMX after 2.8 (I've heard mentions of single-shard atomicity), but by this point we have even bigger and better things than just single-shard transactions planned. > and a few other improvements and Performance Boosting Things. Not sure what you mean. The coolest things I've heard are not storage related, e.g. filtered replication. They're definitely exciting, but unrelated enough that we should be able to just merge them wholesale. > So to what scale with Toku remain relevant if they don't keep up to date with Mongo We'll keep up, don't worry. Here's hoping we maintain---and gain---relevance. ;-) |