MySQL QA

Hi, We are currently running code coverage for MySQL Cluster testing and have hit a few bumps along the road when it cam to collecting the "block" coverage for the NDBD. I wanted to share them here for others that might run into similar frustrations when doing testing code coverage. Gcov accumulates during each run information on which functions and lines of code are called and a total for the times called. The problem comes from when gcov dumps this information out. The actual data is dumped on the "exit" of the program. After much time tracking this issue down, it turns out that the NDBD code had been changed to use _exit() instead of just exit() What is the difference? exit() Terminate the process after cleanup. _exit() Terminate process immediately. So by calling _exit(), gcov never had a chance to dump the data that it had collected. So the quick workaround to this is to wrap all the _exit() calls with an #ifndef i.e. #ifndef HAVE_gcov _exit(0) #else exit(0...

Hi, First let me start by making sure you know Sun's MySQL Cluster 7.0 has been released as GA. The was announced at the MySQL Users Conference this week. You can read more about the release at: http://www.mysql.com/products/database/cluster/ http://www.mysql.com/news-and-events/generate-article.php?id=2009_06 Now, on to the topic. Disclaimer: All performance numbers released here are used for development purpose only and are not intended for marketing. The systems are not set for optimal throughput and the results of tests are "only" used to ensure that we have not lost performance from commit to commit or to, as in this case, track down issues. Moreover, the TPC-"B" test is a retired test from www.tpc.org, but is still a very useful test when looking at simple transaction and scalability of simple transactions w/ a low probability of deadlocks and rollbacks. Results for other users or customers may vary and each should try different combination of options to s...