Request a Service Key for the Performance Monitor for MySQL

To provide you a correct configuration and to grant you access to our system we need some information from you.

Fields marked with an asterisk (*) are required.

On December 2^nd 2011 FromDual released the new version v0.7.2 of its Performance Monitor for MySQL. The new version can be downloaded from here.

The Performance Monitor for MySQL is an agent which is hooked into the agent of the well known Monitoring solution called Zabbix. Zabbix is an integrated Enterprise Monitoring solution which can produce performance graphs and alerting.

The changes in the new release are:

New functionality

Abstract: In this article we provide a little JMeter WebShop Example Benchmark for MySQL.

For our Advanced MySQL Developer Workshop we have one exercise Benchmarking MySQL with JMeter. For this exercise we are using the FoodMart-2.0 [1] Schema and simulating a simple WebShop Transaction:

Abstract: In this article we discuss how big is the performance impact of MySQL TRIGGERs compared to application side logging (with INSERT) into a MySQL table.

The FromDual Performance Monitor for MySQL has now a new module for monitoring DRBD. Since more an more of our customers want to run MySQL High Availability solutions based on DRBD we have implemented this module.

We gather all information which are reported with the command:

Be careful when using SAN (Storage Area Networks) or similar shard storage solutions (and any other virtualization, consolidation or cloud solutions).

This week it happened again: A customer called us because he had some troubles with his on-line shop (note the date!). Everybody in his company complained that the databases are answering slowly.

Vorsicht bei der Nutzung von SAN (Storage Area Networks) oder ähnlichen Shard Storage Lösungen (und allen anderen Virtualisierungs-, Konsolidierungs- oder Cloud-Lösungen).

FromDual releases its new version v0.5 of its MySQL Performance Monitor working with Zabbix.

What has changed so far in this release:

• Recommended Location has changed to /usr/local
• FromDual agent log files are rotated now.
• There are now 2 different packages: One for the Agent and one for the Templates.
• Some of the graphs were improved.
• Missing status and system variable information were added and some were fixed.
• Verbosity of logging information was adjusted.

It is generally well known that indices help a lot to speed up database queries (especially SELECT but also UPDATE and DELETE). It is less known, that indices also have some disadvantages.
One of these disadvantages is, that indices require space in memory and on disk. An other disadvantage of indices is, that they slow down DML statements like INSERT and DELETE.

We often see at our customers that they do not realized this behaviour. Now I found the time to show the impact of (too) many indices graphically.

In the following test scenario we created a simple table:

FromDual launches its database Performance Monitoring solution for MySQL / MariaDB. This solution provides monitoring capabilities for most MySQL Storage Engines (Aria, InnoDB, MyISAM, NDB, PBXT and XtraDB). Further you can monitor MySQL Master - Slave replication set-ups, UNIX processes (mysqld, ndbd) and MySQL/MariaDB specific information.

FromDual veröffentlicht seine Datenbank Performance Monitoring Lösung für MySQL / MariaDB. Diese Lösung verfügt über Monitoringmöglichkeiten für die meisten MySQL Storage Engines (Aria, InnoDB, MyISAM, NDB, PBXT und XtraDB). Im Weiteren können MySQL Master - Slave Replikationen, UNIX Prozesse (mysqld, ndbd) und MySQL/MariaDB spezifische Informationen überwacht werden.

What is the FromDual Performance Monitor for MySQL?

The FromDual Performance Monitor for MySQL, Percona Server and MariaDB is a Monitoring Solution based on the Enterprise open source Monitor Zabbix.
It provides all the necessary modules to monitor MySQL performance metrics in detail an let you display them graphically.
Thus it is a good alternative to the MySQL Enterprise Monitor which is only available for paying Oracle/MySQL customers.

This MySQL Performance Tuning Key should give you a guide how to best tune you MySQL or MariaDB database systematically... It should also work similar for other RDBMS.

Also check our MySQL Performance Monitor

For a database configuration tuning only please look first at our MySQL/MariaDB database health check.

General things about benchmarking

• RAID, bm and bonnie Benchmarks
• xCAT HPC Benchmark HOWTO (WIP)
• Speeding up Linux Using hdparm

General benchmarks

• bm

Disk benchmarking

• Filesystem Benchmark: IOzone
• Bonnie
• Harddisk-Benchmark: Bonnie++
• [http://www.

We have had the following presentations:

Release v0.27

• On this page you can check the health of your MySQL/MariaDB database.
• If you want to find out how the MySQL Health Check works try out the examples.
• If you are logged in, our CMS remembers your entry for your next visit.
• If we should send you some advices about the findings please fill in the following form:

mysql> SHOW /*!50000 GLOBAL */ STATUS;

mysql> SHOW GLOBAL VARIABLES;

shell> grep -c processor /proc/cpuinfo

shell> free -m | grep Mem | awk '{ print $2 }'

shell> uname -m

It is possible to use an active - active shared-disk cluster in MySQL in some cases. For doing this you have to fulfil the following requirements:

• Works with MyISAM tables only.
• POSIX-locking compliant cluster file system on the device (such as OCFS2 or GFS).
• External locking must be enabled.
• The MySQL query cache must be turned off.
• The MySQL delay key write must be turned off.
• OS where file locking is supported in MySQL.

Interested?

Transaction performance relates among other things from I/O performance. This means hard disk performance.

Hard disk performance

When you select a hard disk, an important feature to consider is the performance (speed) of the drive. Hard disks come in a wide range of performance capabilities. As is true of many things, one of the best indicators of a drive’s relative performance is its price. An old saying from the automobile-racing industry is appropriate here: "Speed costs money.

The price for a 160 Gbyte disk will be around USD 15'000. This is still a bit expensive. But the access time is around 0.5 ms (both for reading and writing) which is around 10 times faster than a normal 15'000 rpm SCSI disk! The disk has NO cache because it is a cache itself (according to the supplier. Maybe this will change in the future). And the lifetime of a cell is > 5 mio writes. For the same performance one needs usually an array of around 10 disks. If your database is heavily write-I/O bound you should consider this solution.

I/O-Systems

Materialised View (MV) is the pre-calculated (materialised) result of a query. Unlike a simple VIEW the result of a Materialised View is stored somewhere, generally in a table. Materialised Views are used when immediate response is needed and the query where the Materialised View bases on would take to long to produce a result. Materialised Views have to be refreshed once in a while. It depends on the requirements how often a Materialised View is refreshed and how actual its content is.