I previously tested InnoDB on an 8-core server to determine how many IOPs it can do for a simple IO-bound workload. The limits were ~12k disk reads/second for MySQL 5.0 and ~18k reads/second for MySQL 5.1. I just repeated the tests using a 16-core server and the results are much better. I can get 20,000 to 30,000 disk reads/second using InnoDB 5.1. InnoDB 5.5 appears to be capable of 50,000 to 70,000 disk reads/second courtesy of support for multiple buffer pools (innodb_buffer_pool_instances). This is possible on benchmarks assuming sufficient concurrency and without unreasonable degradation in response time. This is a best-case result that is unlikely to be achieved in production, but I much prefer a best case of 30,000 disk reads/second instead of 10,000/second.

The test runs 1 to 1024 concurrent threads on a client server. Each thread fetches one row per …

Oracle Open World is the conference of everything related to Oracle. This year edition, running from September 19th to 23rd, is expected to have more than 45,000 attendees, making it one of the biggest IT events worldwide.

Traditionally, on the Sunday preceding the main event, there is a full day technical event, fueled by the user groups, independently from the company. These Sunday events are wildly popular. they are organized by users for users, and these sessions are usually fully attended.

Now that MySQL is part of the Oracle portfolio, it is going to be part of the Oracle Open World show. In the spirit of the user groups events, there will be a MySQL Sunday event on Sunday afternoon, with four highly technical tracks, with well known speakers. …

Devart today releases dbForge Studio for MySQL, v4.50 – cutting-edge administration tool and development environment for professional working with MySQL databases.

With dbForge Studio, Devart continues its initiative to produce efficient database experiences for all the people in MySQL world.

New features in dbForge Studio for MySQL, v4.50 include:

More freedom for backing up schemas

Schema Export wizard has been totally redesigned to Database Backup to enable users to back up schemas in automatic mode using Windows task scheduler, save backup options for future use, view automatically complied log file. Besides old backup files are automatically removed based on date or quantity.

…

For the last few years I have had an interest in configuration management of IT infrastructure. While by no means an expert I have a considerable amount of experience with the problems associated with mass server configuration and have come to believe it also one of the most under-served disciplines in systems management.

In a previous life I had an operations role maintaining primarily Linux servers and other open source infrastructure. In 2006 I worked on launching the open source NetDirector project, a graphical tool for configuring open source infrastructure like Apache, Samba, LDAP and NFS servers. During that time the challenges of …

Dear Community,

Percona Server version 5.1.47-rel11.0 is available for download now.

The changes in this release include:

New features

• Percona Server is now based on MySQL 5.1.47, and XtraDB is now based on InnoDB plugin 1.0.8.
• XtraDB now uses the fast recovery code released in InnoDB Plugin version 1.0.8, instead of Percona's earlier fast-recovery code.
• Added the --percona_innodb_doublewrite_path option to place the double-write-buffer into its own file (issue #584299). The feature is sponsored by Large Social Network website.
• Added the --suppress_log_warning_1592 option to disable …

We are pleased to announce the availability of the 1.5.0 RC 1 release of InfiniDB Community Edition.  This is our initial release candidate for 1.5.  You may notice that we've changed the labeling from 1.1 to 1.5 with this release.  In reviewing the amount of functionality that has been added since 1.0, we feel that the 1.5 label is warranted.  We will have a second release candidate followed by our 1.5 Final release in early July.  

Th...

For the replication project that I am currently working on in MariaDB, I wanted to understand exactly what information is needed to do full replication of all MySQL/MariaDB statements on the level of completeness that existing replication does. So I went through the code, and this is what I found.

What I am after here is a complete list of what the execution engine needs to provide to have everything that a replication system needs to be able to completely replicate all changes made on a master server. But not anything specific to the particular implementation of replication used, like binlog positions or replication event disk formats, etc.

The basic information needed is of course the query (for statement-based replication), or the column values (for row-based replication). But there are lots of extra details needed, especially for statement-based …

1. Law of Success 2.0 -- a blog of interviews with famous and/or interesting people, from Brad Feld to Uri Geller.
2. Pioneer One -- crowdsourced funding for TV show, perhaps a hint of the future. Pilot shot for $6,000 which was raised through KickStarter. Distributed via BitTorrent.
3. DrasticTools -- PHP/MySQL visualisation tools, including TreeMap, tag cloud, hierarchical bar chart, and animated list. (via TomC on Delicious)
4. GoogleCL -- command-line interface to Google services. At the moment the services are Picasa, …

So William was asking on twitter how to best deploy symfony apps to a cluster of servers. There are actually some nice deployment tools inside the symfony cli that ease deployment to a single server, but that doesn't really cover the cluster case. Actually I assume that if you have a cluster of servers the best deployment strategy should probably be optimized against your specific use case. But let's make this question a bit more general: How do you deploy updates to your PHP apps running a clustered setup? What architecture do you pick? How do you keep the site running with as few limitations as possible during the update? How do you distribute the new code? How do you clean and prime your caches? How do you handle DB changes? How do you ensure that the DB and code changes do not get in the way of each other?

Obviously the choice of RDBMS can play a big role …

A couple of question I get a lot from MySQL customers is “how will this hardware upgrade improve my transactions per second (TPS)” and “what level of TPS will MySQL perform on this hardware if I’m running ACID settings?” Running sysbench against MySQL with different values for per-thread and global memory buffer sizes, ACID settings, and other settings gives me concrete values to bring to the customer to show the impact that more RAM, faster CPUs, faster disks, or cnf changes have on the server. Here are some examples for a common question: “If I’m using full ACID settings vs non-ACID settings what performance am I going to get from this server?”

Let’s find out by running sysbench with the following settings (most are self explanatory – if not the man page can explain them):

• sysbench –test=oltp –db-driver=mysql –oltp-table-size=1000000 –mysql-engine-trx=yes –oltp-test-mode=complex …