Live data from Hacker News

How To Make An Infinitely Scalable RDBMS

highscalability.com

91–92 of 92 posts

Re: How To Make An Infinitely Scalable RDBMS

#91

What is the difference to Teradata or Netezza except this is open source and lack the burden of universality yet?

Those are analytics databases, also known as data warehouses. Optimized for batch reporting. InfiniSQL is geared for operational/transactional (OLTP) kinds of workloads.

Re: How To Make An Infinitely Scalable RDBMS

#92
post #90
post #87

Earlier quoted context omitted.

What do you base your performance claim vs Clustrix on?

Here is some back of napkin analysis: Starting with this benchmark report: http://www.percona.com/files/white-papers/clustrix-tpcc-mysq... Basically, InfiniSQL does not currently support complex indices, so it can't do a TPC-like transaction. The maximum throughput on 9 nodes is 128,114 per node per second. I don't know if that's 4 or 8 core nodes. If roughly 10% of transactions are multi-node transactions, then 12,8…

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 would substantially change the numbers.

2. The tpcc workload is much more complex than your benchmark. It doesn't make sense to compare a tpcc transaction, of which there are multiple flavors, to your workload.

3. All Clustrix write transactions are multi-node transactions. There's a 2x data redundancy in the test. We do not have a master-slave model for data distribution. Docs on our data distribution model: http://docs.clustrix.com/display/CLXDOC/Data+Distribution.

-----

Now we've also done tests where the workload is a simple point updates and select on memory resident datasets. For those kinds of workloads, a 20 node cluster can do over 1M TPS.

Post reply on HN