I’ve done some benchmark testing of 2 Python modules for MySQL data retrieval: MySQLdb and pyhs. MySQLdb uses MySQL’s client libraries, whereas pyhs uses HandlerSocket that bypasses MySQL’s client layer and interfaces Innodb storage engine’s files directly. In my testing, HandlerSocket results in 82% improvement over mysql client libraries based on number of rows retrieved. The tests were conducted under different conditions: right after a start when cache is cold, a warmed up cache after running SELECT * FROM customer, and alternating the execution order of those 2 Python files. The results are fairly consistent in that they all fall in the same range. …

Vim or vi is a text editor. It can be used to edit all kinds of plain text. It is especially useful for editing programs or UNIX/Linux configuration files.Turn on syntax highlighting:
Open file (for example test.sh):$ vi test.shNow press ESC key to enter into command mode then type  ” : syntax on OR syn on”:syntax onOR:syn onThat’s it.. the color syntax highlighting will be enabled until you close that file (useful when you working on server where you can’t enable it permanently because of restriction and not having desired access of .vimrc file.)
Turn off syntax highlighting:
Press ESC key to enter into command mode then type “: syntax off OR syn off”:syntax offOR: syn off
Enable color syntax highlighting permanently:
You may need to add "syntax on" (or "syn on") in your $HOME/.vimrc file$ vi …

Despite the fact that dbForge products were developed only for Windows platforms, our active users (thanks to Tsvetkov) have found a way to use some features of dbForge Studio for MySql on Linux family operating systems.

Tests were run under .Net Framework 2.0 on Wine emulator.

The following command line functionality works with no visible issues:

• /backup – backups a database
• /restore – restores a database
• /datacompare – launches a data comparison
• /datacompare /sync – launches a database synchronization
• /schemacompare – launches a schema comparison
• /schemacompare /sync – launches a database synchronization
• /dataexport (starting from version 5.0) – exports data
• /dataimport (starting from version 5.0) – imports data
…

Despite the fact that dbForge products were developed only for Windows platforms, our active users (thanks to Tsvetkov) have found a way to use some features of dbForge Studio for MySql on Linux family operating systems. Tests were run under .Net Framework 2.0 on Wine emulator. The following command line functionality works with no visible [...]

I have been writing a bit about Gearman lately, including installing it for PHP and Ubuntu, actually using it from PHP and also how I use persistent storage with Gearman. I'm moving on to look at adding jobs of different priorities.

I use Gearman entirely as a point to introduce asynchronous-ness in my application. There is a complicated and image-heavy PDF to generate and this happens on an automated schedule. To do this, I use the GearmanClient::doBackground method. This inserts a priority 1 job into my queue. …

fisl12 is likely the largest free and open source software event in Latin America. This year, it takes place in Porto Alegre, Brazil, from June 29th to July 2nd. Oracle is a gold sponsor of the event and I will attend it as a speaker. I feel honoured and excited to be there – for me it will be the first visit to the South American continent.

They already have over 3000 registered attendees, so this definitely is going to be a great conference. There is quite a number of well-known names on the speaker roster and I look forward to meeting a lot of familar faces there.

The agenda is still under development but quite impressive already – …

It's been a while since my last post on this blog; I definitely need to get back into the habit! One of the reasons for my radio silence was that I switched roles here at Oracle. After having been with the MySQL team for 9 years, I felt it was time for a change. Fortunately I did not have to look far – I'm now a member of the Oracle Linux product management team and I am having a lot of fun there.

However, I realized that while I was an active Linux user on the desktop, quite a lot has happened on the enterprise and data center side of things. Linux has really come a long way and I am glad to be back in this field, drinking from the firehose and learning a lot about recent developments and technologies. For me, this is kind of going "back to my roots", as I have been deeply involved with Linux at SuSE before I joined MySQL in 2002.

Anyway, I'm still alive and you can expect …

Apache OpenOffice.org proposal approved. SkySQL Tekes new funding. And more.

# The proposal for OpenOffice.org to become an Apache incubator project was unanimously approved.

# Rob Weir discussed how the relationship between OpenOffice.org and LibreOffice need not be a zero-sum game.

# Simon Phipps offered his thoughts on the potential positive and negative outcomes.

# Tekes, the main public funding agency for research, development, and innovation in Finland, …

The SELF Linux show ramps up to full swing tomorrow. We will have the new MySQL 5.5 shirts as well as Linux shirts. Please stop by say hi and get a shirt while they last!
I was glad to see the support for MySQL on day one, can't wait until tomorrow.
http://www.southeastlinuxfest.org/

Mythbusters: How to configure InnoDB buffer poll on large MySQL servers

Yesterday I wrote about the dangers in using top on systems with 100+ GB of RAM, not to mention future systems with 1+ TB. A related topic is, how should I configure MySQL on such a large system?

There is a classic rule of thumb that on a dedicated MySQL server one should allocate 80% of memory to the InnoDB buffer pool. On a 128GB system that is 102.4 GB. This means that I would leave 25.6 GB of RAM "unused". So surely on these large systems, this old piece of advice cannot hold anymore. If the database was previously running on a server that in total had less than that altogether, it seems wrong to leave so much memory just unused. Let's label the old rule of thumb tentatively a "myth" and ask mythbusters to figure out a new MySQL configuration …