Dear interweb, if you have no idea what you’re writing about, keep it to yourself, don’t litter into the tubes. Some people may not notice they’re eating absolute crap and get diarrhea.

This particular benchmark has two favorite parts, that go with each other together really well:

I didnt change absolutely any parameters for the servers, eg didn’t change the innodb_buffer_pool_size or key_buffer_size.

And..

If you need speed just to fetch a data for a given combination or key, Redis is a solution that you need to look at. MySQL can no way compare to Redis and Memcache. …

Seriously, how does one repay for all the damage of such idiotic benchmarks?

P.S. I’ve ranted at benchmarks before, and will …

I wanted to compare the following DBs, NoSQLs and caching solutions for speed and connections. Tested the following

• Redis
• Memcached
• Tokyo Tyrant / Tokyo Cabinet
• MySQL 5.1.40 (MyISAM)
• MySQL 5.1.40 (with Innodb Plugin 1.0.4), compiled into source of MySQL

My test had the following criteria

• 2 client boxes
• All clients connecting to the server using Python
• Used Python's threads to create concurrency
• Each thread made 10,000 open-close connections to the server
• The server …

Désolé, il ne reste plus de place pour cette matinée dédiée à l'optimisation des performances MySQL.

Date : 24 novembre 2009

Session 1 : 9h30-10h45

• Architecture MySQL : Parsing, exécution, optimizer, query cache, binlog…etc
• Architecture Innodb : Clustered index, bufferpool, hash index, insert buffer, locking model, MVCC, recovery log, checkpoint…etc. Comparaison avec les autres moteurs de stockage (PBXT, MySQL Cluster) et bases de données (PostgreSQL, Oracle ..).

Pause/Café : 10h45-11h00.

Session 2 : 11h00-12h30

• Évolutions récentes : Google SMP patches,  XtraDB, Oracle innodb plugin 1.0.4
• Apports de MySQL 5.4
• Améliorations à venir :  Ahead flushing / Adaptive checkpoint,  …

Recently I looked at table_cache sizing which showed larger table cache does not always provides the best performance. So I decided to look at yet another similar variable - innodb_open_files which defines how many files Innodb will keep open while working in innodb_file_per_table mode.

Unlike MyISAM Innodb does not have to keep open file descriptor when table is open - open table is purely logical state and appropriate .ibd file may be open or closed. Furthermore besides MySQL table_cache Innodb maintains its own (called data dictionary) which keeps all tables ever accessed since table start - there is no variable to control its size and it can take significant amount of memory in some edge cases. Percona patches though provide innodb_dict_size_limit to restrict …

Like I said earlier, every tiny change that the test suite reveals after code changes is significant. I caught a very subtle “bug” today in recent changes to mk-query-digest (a.k.a. mqd). If you like to read about subtle bugs, read on.

An mqd test on sample file slow023.txt began to differ after some pretty extensive code changes of late:

< # Query 1: 0 QPS, 0x concurrency, ID 0x8E38374648788E52 at byte 0 ________
---
> # Query 1: 0 QPS, 0x concurrency, ID 0x2CFD93750B99C734 at byte 0 ________

The ID which depends on the query’s fingerprint has changed. It’s very important that we don’t suddenly change these on users because these IDs are pivotal in trend analyses with mqd’s --review-history option. First some background info on the recent code changes and then the …

We are pleased to announce the availablity of the 0.9.5.1 alpha release of InfiniDB Community Edition.  This is our latest alpha release and is not recommended for production work. 

New functionality we’ve added with 0.9.5.1 includes:  

Support for union and union all. 
Support for 23 new distributed functions.   
Cleanup of system catalog reduces disk usage on new installs.
Support for GCC 4.4 and Ubuntu 9.10.

There have been times that I needed to restore one database from a dump file that contains all of the databases from the server. There are a few ways to accomplish this goal. One way would be to grep through the entire file for the table schema and insert statements. There are some problems with this method in some environments. For example, what if a table name in the targeted databases had the same name in another database on the same instance? The logic for grep now gets increasingly more complex.

It’s a good thing that the developers at MySQL already thought of this and implemented it, --one-database. In the example below I have created 4 databases, test, test[1-3] and filled each of them with 10K rows. I run mysqldump for all databases and put them in a file called test.all.sql then truncate test2.tbl1. Using …

by @botchagalupe
on Virtualization, Open Source tools and DNS Problems

Technorati Tags: dnsproblem drupal ha heartbeat linux-ha mysql pacemaker puppet virtualization xen …

MySQL Workbench 5.2 introduces a lot of new functionality and therefore this short tutorial will help you to get started quickly.

The Home Screen

The most prominent new addition in respect to previous Workbench releases is the new Home Screen. It allows you to access the main features of Workbench in a nice and easy way and is divided into 4 parts.

The upper Workbench Central panel features a few Links and Action Buttons to quickly access common resources.

The lower Workspace panel shows the main feature sets, grouped horizontally.

• SQL Development allows editing and execution of SQL queries and scripts, create or alter database objects and edit table data.
• Data Modeling covers the EER Modeling functionality you might already be familiar with from previous MySQL Workbench releases.
• Server …

Dear MySQL Users,

We are proud to announce that we have reached the Beta 1 for MySQL Workbench 5.2. Beta 1 is “functionally complete” and shows the new features for the upcoming version of Workbench GUI product.

The team has worked very hard to reach the goal of including all our new features within this first public beta version. We know there is still a lot of fine tuning and stabilization to be done over the coming weeks to get it solid on all platforms, but this release marks an important milestone.  Your beta feedback is key to this.

MySQL Workbench 5.2 Beta 1 provides:

1. Data Modeling
2. Query (upgrade from MySQL Query Browser)
3. Admin (upgrade from MySQL Administrator)

If you are a current user of MySQL Query Browser or MySQL Administrator, we look forward to your feedback on all the new capabilities we are delivering in a single unified MySQL Workbench …