Being the one that wrote the code: I'm with you too (in a way...) The thing is that prior to this release, applications that were using SQL joins (involving more than 2 tables) where ruled OUT: Now a lot of more applications *can* use MySQL Cluster.
That is the new feature...but 70x is what's in the press release.
(NOTE: mysql cluster is a different prodcut from mysql server)
ok...so here is confusion....the press release mentions 2 distictly different things. 1) upto 70x faster joins
this did not use the 100 byte records,
this did use ordinary ethernet 2) 1B QPM
this used 100 bytes records
this used infiniband
this use single row transactions (NoSQL type benchmark)
which previously were quite poorly handled. See http://www.clusterdb.com/mysql-cluster/70x-faster-joins-with-aql-in-mysql-cluster-7-2/?utm_source=rss&utm_medium=rss&utm_campaign=70x-faster-joins-with-aql-in-mysql-cluster-7-2
Actually we have implemented disk storage. Hopefully it will make into version 5.1.
MySQL Cluster 4.1/5.0 supports: * transactions * transparent data partitioning and transparent data distribution * recovery using logging * (multi) node failure and automatic non blocking hot sync for crashed/stopped nodes * hot backup
MySQL Cluster 5.1 will support: * user defined partitioning * cluster to cluster async. replication (like "ordinary" mysql replication)
The disk impl. supports * support putting column in memory or on disk
(currently index columns has to be in memory) * all HA features mentioned above.
Slashdot Mirror
he he...do you have illegal survailance of my desk ? /Jonas MySQL Cluster developer
Being the one that wrote the code: I'm with you too (in a way...)
The thing is that prior to this release, applications that were using SQL joins (involving more than 2 tables) where ruled OUT:
Now a lot of more applications *can* use MySQL Cluster.
That is the new feature...but 70x is what's in the press release.
(NOTE: mysql cluster is a different prodcut from mysql server)
ok...so here is confusion....the press release mentions 2 distictly different things.
1) upto 70x faster joins
this did not use the 100 byte records,
this did use ordinary ethernet
2) 1B QPM
this used 100 bytes records
this used infiniband
this use single row transactions (NoSQL type benchmark)
which previously were quite poorly handled.
See http://www.clusterdb.com/mysql-cluster/70x-faster-joins-with-aql-in-mysql-cluster-7-2/?utm_source=rss&utm_medium=rss&utm_campaign=70x-faster-joins-with-aql-in-mysql-cluster-7-2
Amiga 500(OCS):
Cebit90 - RedSector
Hardwired - Crionics/Silents
Virtual Intelligence - Horizon
Sounds like a good fit for MySQL Cluster.
1) Data is logged and checkpointed.
So even in case of "a catastrophic UPS failure" data will be there once your power is back.
2) In 5.1 the all data in RAM limitation is removed.
(Except for indexes which still has to reside in RAM)
Actually we have implemented disk storage.
Hopefully it will make into version 5.1.
MySQL Cluster 4.1/5.0 supports:
* transactions
* transparent data partitioning and transparent data distribution
* recovery using logging
* (multi) node failure and automatic non blocking hot sync for crashed/stopped nodes
* hot backup
MySQL Cluster 5.1 will support:
* user defined partitioning
* cluster to cluster async. replication (like "ordinary" mysql replication)
The disk impl. supports
* support putting column in memory or on disk
(currently index columns has to be in memory)
* all HA features mentioned above.