Comments on: Managing Internet Protocol Television Data. — An interview with Stefan Arbanowski. http://www.odbms.org/blog/2012/06/managing-internet-protocol-television-data-an-interview-with-stefan-arbanowski/ Trends and Information on Big Data, New Data Management Technologies, and Innovation. Wed, 17 Apr 2013 21:47:18 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Dimitri http://www.odbms.org/blog/2012/06/managing-internet-protocol-television-data-an-interview-with-stefan-arbanowski/comment-page-1/#comment-7406 Dimitri Mon, 09 Jul 2012 13:34:37 +0000 http://www.odbms.org/blog/?p=1533#comment-7406 Regarding your white paper: Was it intentional to compare with a so old MySQL version?.. there is MySQL 5.5 which is already GA since last year, and MySQL 5.6 which is available as labs release -- both are way better than 5.0.. Then, did you analyze your bottlenecks in MySQL?.. did you try to understand or to tune it? -- using just a default settings as it is not a right thing to do when you're expecting to reach some performance goals (and it's true for any databases, not only MySQL).. As well, from a very few information you're providing, I may suppose you've used MyISAM as storage engine for your tables.. - why did not you use InnoDB, which is high concurrent and truly transactional?.. And then, if you're considering in-memory solutions -- why you did not try MySQL Cluster which is easily giving today 1M TPS even on a single node?.. Well, looks very ugly for me as a comparison and its conclusion.. Rgds, -Dimitri Regarding your white paper:

Was it intentional to compare with a so old MySQL version?.. there is MySQL 5.5 which is already GA since last year, and MySQL 5.6 which is available as labs release — both are way better than 5.0..

Then, did you analyze your bottlenecks in MySQL?.. did you try to understand or to tune it? — using just a default settings as it is not a right thing to do when you’re expecting to reach some performance goals (and it’s true for any databases, not only MySQL)..

As well, from a very few information you’re providing, I may suppose you’ve used MyISAM as storage engine for your tables.. – why did not you use InnoDB, which is high concurrent and truly transactional?..

And then, if you’re considering in-memory solutions — why you did not try MySQL Cluster which is easily giving today 1M TPS even on a single node?..

Well, looks very ugly for me as a comparison and its conclusion..

Rgds,
-Dimitri

]]> By: Robert Friberg http://www.odbms.org/blog/2012/06/managing-internet-protocol-television-data-an-interview-with-stefan-arbanowski/comment-page-1/#comment-7397 Robert Friberg Sat, 30 Jun 2012 05:14:54 +0000 http://www.odbms.org/blog/?p=1533#comment-7397 In the interview 3 implementations are mentioned, including handling data in RAM, which is not described in the whitepaper. Any information about this would be interesting! In the interview 3 implementations are mentioned, including handling data in RAM, which is not described in the whitepaper. Any information about this would be interesting!

]]>