Viewing profile — sergei

Several problems here: 1. Unlike your dataset, the tpcc dataset for the benchmark was not memory resident. Total dataset size was 786G. Just shrinking the dataset to fit in memory …

What do you base your performance claim vs Clustrix on?

I frequently see apps with thousands of distinct query signatures. Having a developer manually chose indexes, join ordering, aggregation method, (just to name a few) for every sing…

In practice, you end up with apps which dynamically build up predicates in different sections of the code. And when you combine that with many predicates, many tables, and other co…

A decent cost based optimizer will be right most of the time, and you have hints for the cases where it falters. Your approach is simply hiding the query optimizer choices inside o…

Check out a previous comment thread on the subject: https://news.ycombinator.com/item?id=5068489

Check out a previous comment thread on the subject: https://news.ycombinator.com/item?id=5068489

Yes, but they are in-memory only. I think the largest database they support is 50GB. It's the kind of solution that works really well if you have key-value store problem where you …

1) Both joins and aggregates are processed in parallel. In short, the larger your cluster, the faster we evaluate a complex query because we can bring more hardware to the problem.…

It's a good question. We built the entire database from the ground up, without any MySQL code. So while we support most of the frequently used features, we don't support everything…

Try it. You'll like it :)

It's different from a typical sharding approach (including what MongoDB does). In their model, you take a single key and distribute your data using that key (e.g. user_id). The pro…

Some reading material on the distributed approach: http://www.clustrix.com/blog/bid/242790/Scaling-Distributed-... http://www.clustrix.com/Portals/146389/docs/clustrix_a_new_a...

We listened to the community and made our database available on AWS. We're currently working on making it available as standalone outside of AWS as well.

San Francisco, CA Clustrix: Systems Developers Clustrix has developed a highly scalable distributed database system from the ground up. We are looking for skilled systems developer…

The problem with Mongo's concurrency approach is that when you introduce writes to the equation (which take out an exclusive lock on the database), the system becomes unusable. Her…

Many responses to my previous post claimed that my comparisons to MongoDB were unfair because MongoDB is a "document store" and Clustrix is a SQL RDBMS. Somehow that distinction ma…

Sorry, but "hardware failure" is a fault, and when you can't deal with it, you're not tolerant. And with larger clusters, you see hardware faults on a regular basis. So saying we'r…

1. Yes, I recognize that MongoDB will automatically fail over when we go from N nodes in the set to N - 1. But how do I get back to N nodes? That's completely manual. 2. What happe…

1. Say I have a 2 node replica set. Now a replica dies, permanently. How is the recovery automated? These are quotes directly from your docs: http://www.mongodb.org/display/DOCS/Re…

The article is not about the DBMS interface. It's about Fault Tolerance (what happens when stuff breaks) and Availability (can I still use my database when there is a fault). Mongo…