Another day at MySQL connect 2012
Written by Marco Tusa   

Today was another good day, but I had a problem with one presentation and keynote.

the "Big Data is a Big Scam: Most of the Time". There is something that is not convincing me in the architecture,

and is mainly base on the lack of numbers and match between requirements and implementation.


The presentation was interesting from some aspects, and the tile approach is probably a good one.


I have enjoy the general idea and I did found awesome the bravery of setting up a circular replication cross geographic regions.


Never the less I remain bewildered by the tiles approach numbers, probably because the presentation was missing of few additional information.


Just to be more clear I was trying to understand better the real number and how works.


As for example if each tile is compose by 1 MySQL node, and 2 data node, and given that this solution use Xtra large EC2 with 68GB ram. I can assume that,

we have approximately 65 GB data (given some overhead for buffers and so on) for the current Node Group on this tile.

From the description I have also understood that the number of tails implemented, is different by region.


Given that the number of Node Group is different and by direct consequence the memory available as well, and the MySQL SQL node as well.


This raise an immediate question, are we having the same data set replicated world wide?


Or are we having a different sets?



each Node Group can host ~69GB, the maximum number of data node in 7.2 is still 48 (http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-ndbd-definition.html), which means that the maximum size that can be served is of 1.3TB for the whole cluster.


Given during the presentation my understanding was that the data set is of 100TB, where are located, now or in the future, the remaining 98.7TB? Keeping in mind that I asks if table on disks where used and answer was NO.

Then I have another question-mark infront of me.

If the set of tiles in US is compose of 20 tiles, (so 20 MySQL SQL Nodes, 40 Data nodes and so on), and it set like this because it needs to sustain the traffic mainly it requires that setting for "calculation power" needs.

I assume (probably wrong) that this is due to the number of request per second coming in.


Given we have circular replication in the architecture, and given we have different numbers of tiles, and by consequence of MySQL nodes, HOW can a 8 MySQL SQL Node setup (say in Australia) sustain the traffic coming in from a 20 MySQL SQL nodes setup?


I am sure, we are missing something in the presentation in terms of real numbers.


Being a MySQL NDB lover, I would really like to have more information and details, given that what I get from the presentation was not enough for me.



Last Updated on Sunday, 18 August 2013 17:24
MySQL Oracle connect 2012 Day one
Written by Marco Tusa   

I attend five session today and I think some of them were very interesting.


Like the one on the Optimizer insight, quite informative and accurate.


The other one done by the MySQL CLuster (NDB) group on the installer and new Javascript API interface, left me a little bit ... foggy. Why? Because in my mind one of the most important thing to accomplish in NDB is the correct dimensioning of the memory, buffers, possible operation, attributes and so on, all things that should come from the review of the schema definition review and from the application analysis.

Now given the review analysis of the schema is still not present in the installer, I think that we mis a very important peace of information.


When I raise the issue, Bernd mention that they are thinking of integrating that as well, good move and I hope to see it soon.


About the javascript API honestly I think this is a real waste of time, but maybe someone will use it.

The next two where from Peter Z. and Vadim, both containing material already saw, and nothing really new.


Last one on MySQL Migration wizard, It is good to see that Oracle decide to revive the project. I was expecting something more then what was presented, given what was there is mainly what was in the old MySQL Migration Toolkit, for the good and for the bed. In short the main work done was to port the code from Delphi,Java lua to Python and C++.


But still the same old issue like data streaming from source to destination using a third element (box) where the tool needs to run.

No control on the data loading status, which in case of crash of the data loading will bound to reload all data from start, and so on.

I think there is a lot of work to do in this project, and I am convince that the developers need a significant help, in order to focus on the real issues that could be the real value of the tool, instead useless cosmetics.

In general the day was good, but my honest impression is that Oracle is in good shape from the product side, but not good in other areas like interaction and presentation with customer and partners.


There is where the great MySQL diaspora had hit Oracle most, but maybe this first conference is the indication of a change of direction.

Last Updated on Sunday, 18 August 2013 17:25

Page 23 of 26

Connecting from

Your IP:


Who's Online

We have 58 guests online

Latest/Most Comments

no comments