21–30 of 35 posts
If only I had some data to fill the wonderful databases available these days.
MySQL Cluster seems like an awesome solution to applications with a high write to read ratio (which applies to several that I currently work on). I'd be curious to hear cases of people successfully using MySQL Cluster and some of its pros/cons in real-life applications.
Definitely an impressive benchmark by any standard. However, there are some things to be aware of: 1) They used Infiniband interconnects. Running on ethernet is likely to yield less impressive results. 2) Their benchmark does simple primary key lookups. If you start doing joins or transactions that need to hit multiple data nodes, things will slow down. Depending on your workload, this may or may not be an issue. 3)…
Definitely an impressive benchmark by any standard. However, there are some things to be aware of: 1) They used Infiniband interconnects. Running on ethernet is likely to yield less impressive results. 2) Their benchmark does simple primary key lookups. If you start doing joins or transactions that need to hit multiple data nodes, things will slow down. Depending on your workload, this may or may not be an issue. 3)…
Has anyone here used MySQL Cluster in production?
Earlier quoted context omitted.
I did try around the time it split from the normal releases (6.0?). The overall feeling I got was that lots of simple things don't work, trivial bugs stay open for... well mine are still open and there was next to no documentation for any kind of troubleshooting. NDB returned error numbers which were not properly translated by mysql_error, so you were left looking them up the hard way. There was also next to no commu…
Yeah, that was pretty much exactly my experience last time I tried it. (Around version 7.1 / mid-2010, I think.)
Since our complexity requirements were low we settled for a home-grown solution (basically memcached with write-through) and so far didn't regret.
I, too, remain curious if anyone is running this at scale and has bumped into the various corner cases (exceeding capacity, hardware dying, etc.).
When did we go from standard measure of per second for these types of things, you know, requests per second, transactions per second, to per minute? Statistics eh?
For whatever reason, database people have been using transactions per minute for a long time.
I'm a novice in this area, so looking past the somewhat sensationalist headline (or, perhaps, I'm missing the wit? "Now with 70x more performance!")... Can someone who knows this stuff give a bit of an overview on the significance of this release? I read the NoSQL stuff as Oracle/MySQL trying to compete (at least in terms of marketing-speak) with the wave of competition that's arrived in the DB market. Is there any m…
Cluster has "sql nodes" (that you query against) and "data nodes" that house the actual data, which "sql nodes" talk to to actually process the query.
Cluster can now tell the data nodes to only return necessary subsets of data back to the "sql nodes" when doing a JOIN, instead of pulling down more information (and filtering on the sql node side) when answering complex JOIN queries.
You can read more about this at "push down" feature at http://www.clusterdb.com/mysql-cluster/trying-out-mysql-push...
Note that the linked article also outlines more about this feature under the heading "70x Higher JOIN Performance with Adaptive Query Localization".
I'm a novice in this area, so looking past the somewhat sensationalist headline (or, perhaps, I'm missing the wit? "Now with 70x more performance!")... Can someone who knows this stuff give a bit of an overview on the significance of this release? I read the NoSQL stuff as Oracle/MySQL trying to compete (at least in terms of marketing-speak) with the wave of competition that's arrived in the DB market. Is there any m…
NDB originally only had a NoSQL interface called NDB API. NDB API is a bit complex and when MySQL acquired them, they added the SQL layer on top of it to make it easier for developers to use it. This release adds an additional memcache api layer which sits on top of NDB API, so that you can more easily program against it.