MySQL Enterprise Monitor 3.0.14 has been released
We are pleased to announce that MySQL Enterprise Monitor 3.0.14 is now
available for download on the My Oracle Support (MOS) web site. It
will also be available via the Oracle Software Delivery Cloud in a few weeks.
This is a maintenance release that includes a few new features and fixes a number of bugs. You can
find more information on the contents of this release in the
You will find binaries for the new release on My Oracle Support. Choose the "Patches & Updates" tab, and then choose the "Product or Family (Advanced Search)" side tab in the "Patch Search" portlet.
You will also find the binaries on the Oracle Software Delivery Cloud in a few weeks. Choose "MySQL Database" as the Product Pack and you will find the Enterprise Monitor along with other MySQL products.
Based on feedback from our customers, MySQL Enterprise Monitor (MEM)
3.0 offers many significant improvements over previous releases.
Policy-based automatic scheduling of rules and event handling (including email notifications) make administration of scale-out easier and automatic
Enhancements such as automatic discovery of MySQL instances, centralized agent configuration and multi-instance monitoring further improve ease of configuration and management
The new cloud and virtualization-friendly, "agent-less" design allows remote monitoring of MySQL databases without the need for any remote agents
Trends, projections and forecasting - Graphs and Event handlers inform you in advance of impending file system capacity problems
Zero Configuration Query Analyzer - Works "out of the box" with MySQL 5.6 Performance_Schema (supported by 5.6.14 or later)
False positives from flapping or spikes are avoided using exponential moving averages and other statistical techniques
Advisors can analyze data across an entire group; for example, the Replication Configuration Advisor can scan an entire topology to find common configuration errors like duplicate server UUIDs or a slave whose version is less than its master's
More information on the contents of this release is available here:
What's new in MySQL Enterprise Monitor 3.0?
MySQL Enterprise Edition: Demos
MySQL Enterprise Monitor Frequently Asked Questions
MySQL Enterprise Monitor Change History
More information on MySQL Enterprise and the Enterprise Monitor can be
If you are not a MySQL Enterprise customer and want to try the Monitor
and Query Analyzer using our 30-day free customer trial, go to
http://www.mysql.com/trials, or contact Sales at
If you haven't looked at MEM recently, and especially MEM 3.0, please
do so now and let us know what you think.
Thanks and Happy Monitoring! - The MySQL Enterprise Tools Development Team
MySQL Enterprise Backup 3.11.0 has been released!!
MySQL Enterprise Backup team is glad to announce the new release of MySQL Enterprise Backup (MEB) 3.11.0.
MEB 3.11.0 focuses on enhancing backup/recovery performance and adding new features that would help database administrators.
This release addresses some of the challenges customers face today while taking backups of very large databases(in terrabytes). This release also provides more complete backup with all the necessary logs required to clone a server. We have also added online restore of tables in 3.11.0 to help DBAs fix corrupted tables in the server from existing backups.
MEB 3.11.0 also brings in cloud support for backup and restore. To meet the growing trend of cloud storage, we released this feature in July '14 as part of MEB 3.10.2 release.
Please refer to this blog on Cloud Storage
MySQL database backed up and restored in cloud
Amazon S3 supported
Simplifies backup and restore of huge database with infrequently modified tables
Backup performance enhanced with smaller redo logs
Full Instance Backup
Complete backup of MySQL with binary logs and relay logs
Cloning of MySQL server (master/slave)
Binary logs consistent with backup, very useful to perform PITR(Point In Time Recovery)
Online selective restore
Online restore of single or multiple tables from TTS backups
Very useful for the DBAs to replace a corrupted table on an online server
MEB 3.11.0 release also contains quite a few important bug fixes for the customers.
Please refer 3.11.0
documentation for more details.
Very soon you will hear detailed blogs from the MEB Engineering team on all the new features introduced in 3.11.0.
MEB 3.11.0 is supported on the following platforms:
- Debian 6.0, RHEL 6, RHEL 7, Oracle Linux, Suse 11,Ubuntu 12.04
- Solaris 10 Sparc/x86, Solaris 11 Sparc/x86
- MacOS 10.6
MEB 3.11.0 is now available in My Oracle Support and will soon be available in Oracle Cloud Delivery.
Using sysbench 0.5 for performing MySQL benchmarks
Given the recent excitement & interest around OpenStack I wanted to make sure I was ready to conduct appropriate evaluations of system performance. I generally turn to sysbench since it comes with a variety of different tests (accessed via –test= option interface), including:fileio – File I/O testcpu – CPU performance testmemory – Memory functions speed testthreads – Threads subsystem performance testmutex – Mutex performance testAs you can see, sysbench lets you stress many of the fundamental components of your hardware and infrastructure, such as your disk subsystem, along with your CPUs and memory. An additional option exists that is designed to perform synthetic stress testing of MySQL, and I was surprised when I didn’t see it in the above list on version 0.5, as it used to show up as “oltp – OLTP test”. What happened to –test=oltp ??This list is from the latest release of sysbench which is 0.5 — you’re only going to be on this version if you build it yourself or if you use the package provided courtesy of Frederic Descamps (thanks lefred!). If you’re using the version from EPEL, Ubuntu 14.04, or Debian 7 you’re still using version 0.4.12 (check with sysbench –version). One thing you’ll notice is that the test type of OLTP doesn’t show up anymore. What gives? I was scratching my head until I asked on Percona IRC and found out that in 0.5 the standard OLTP test type was replaced with a different syntax, that instead of passing parameters to sysbench you instead reference scripts written in lua. The advantage here is that now you have an interface in order to write your own specific load tests (provided you know lua, but it isn’t hard). For those of you looking to run the pre-canned load tests they still exist but you have to have them as part of the RPM install or otherwise copied to your system.Fortunately if you use the package provided by lefred you’ll find these lua scripts here (this is using Amazon ami as of August 4th, 2014):[root@pxc-control ~]# ls -l /usr/share/doc/sysbench/tests/db/
-rw-r--r-- 1 root root 3585 Sep 7 2012 common.lua
-rw-r--r-- 1 root root 340 Sep 7 2012 delete.lua
-rw-r--r-- 1 root root 830 Sep 7 2012 insert.lua
-rw-r--r-- 1 root root 2925 Sep 7 2012 oltp.lua
-rw-r--r-- 1 root root 342 Sep 7 2012 oltp_simple.lua
-rw-r--r-- 1 root root 425 Sep 7 2012 parallel_prepare.lua
-rw-r--r-- 1 root root 343 Sep 7 2012 select.lua
-rw-r--r-- 1 root root 3964 Sep 7 2012 select_random_points.lua
-rw-r--r-- 1 root root 4066 Sep 7 2012 select_random_ranges.lua
-rw-r--r-- 1 root root 343 Sep 7 2012 update_index.lua
-rw-r--r-- 1 root root 552 Sep 7 2012 update_non_index.luaSo the trick (if you want to call it that) is that instead of passing a single word to the –test directive, instead you pass the full path to the lua script.This is the old way (sysbench 0.4.12 from EPEL repo):--test=oltp --oltp-test-mode=complexThis is the new way (sysbench 0.5):--test=/usr/share/doc/sysbench/tests/db/insert.luaHere is an example of a test I’m running through haproxy against a 3-node PXC cluster doing the INSERT-only test type so you can see the full syntax I pass to sysbench:[root@pxc-control ~]# cat sys_haproxy.sh
$1And here’s what the insert.lua script looks like:[root@pxc-control ~]# cat /usr/share/doc/sysbench/tests/db/insert.lua
pathtest = string.match(test, "(.*/)") or ""
dofile(pathtest .. "common.lua")
table_name = "sbtest".. sb_rand_uniform(1, oltp_tables_count)
if (oltp_auto_inc) then
i = 0
i = sb_rand_uniq(1, oltp_table_size)
k_val = sb_rand(1, oltp_table_size)
c_val = sb_rand_str([[
pad_val = sb_rand_str([[
rs = db_query("INSERT INTO " .. table_name .. " (id, k, c, pad) VALUES " .. string.format("(%d, %d, '%s', '%s')",i, k_val, c_val, pad_val))
endThe thing that I like most about sysbench 0.5 (beyond the lua interface, of course!) is that it now comes with a –report-interval option (which I generally set as = 1) so that you get output while the script is running. No more waiting until the end of the test to get feedback! Here’s a sample of sysbench 0.5 in action running the INSERT test through a local haproxy instance and writing to three nodes in a PXC cluster such as OpenStack Trove might do:[root@pxc-control ~]# ./sys_haproxy.sh run
sysbench 0.5: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 3
Report intermediate results every 1 second(s)
Random number generator seed is 0 and will be ignored
[ 1s] threads: 3, tps: 0.00, reads/s: 0.00, writes/s: 1099.28, response time: 9.86ms (95%)
[ 2s] threads: 3, tps: 0.00, reads/s: 0.00, writes/s: 973.02, response time: 10.77ms (95%)
[ 3s] threads: 3, tps: 0.00, reads/s: 0.00, writes/s: 1181.01, response time: 6.23ms (95%)
[ 4s] threads: 3, tps: 0.00, reads/s: 0.00, writes/s: 1103.00, response time: 6.77ms (95%)I would also like to call your attention to a blog post by Nilnandan Joshi from Percona’s Support team where he describes a method to build sysbench 0.5 on Debian 7. Thanks Nil for pointing this out!I hope that helps others out there who upgrade to sysbench 0.5 and then have questions about where –test=oltp went to. I’d love to hear your own sysbench use cases, and whether anyone else is publishing lua scripts for their own load testing!The post Using sysbench 0.5 for performing MySQL benchmarks appeared first on MySQL Performance Blog.
Upscene releases Database Workbench 5
Upscene Productions is proud to announce the availability of the next major
version of the popular Windows based multi-DBMS development tool:
" Database Workbench 5 "
There have been numerous improvements to existing tools and the new, more
consistent user interface is better than ever and works fine under Wine on Linux.
Database Workbench now comes in multiple editions with different
pricing models, there's always a version that suits you!
"There is so much new in Database Workbench 5, I don't know where to start", says Martijn Tonies,
founder of Upscene Productions. "This release adds code editor features, has diagramming improvements,
comes in multiple editions, is fully HiDPI aware and offers tunnelling for MySQL and MariaDB connections. It all was a lot of work, but it was worth it!"
"We worked closely with out customer and implemented many of their requests and for
new users, we offer multiple editions to suit their development needs. From design to
productivity, there's new features and improvements in almost everything!"
For more information, see
What's new in Database Workbench 5?
Database Workbench supports MySQL, MariaDB, Firebird, Oracle, MS SQL Server,
SQL Anywhere, NexusDB and InterBase, comes in multiple editions and is licensed based on
About Database Workbench
Database Workbench is a database developer tool, over 10 years in the making and
is being used by thousands of developers across the globe who have come to rely on it
every day. From database design, implementation, to testing and debugging, it will aid you
in your daily database work.
About Upscene Productions
Based in The Netherlands, Europe, this small but dedicated company has been providing
database developers with useful tools for over 12 years. Slowly expanding the product portfolio
and gaining recognition amongst InterBase and Firebird database developers, they now offer
tools for a hole range of database systems, including Oracle and Microsoft SQL Server.
Making MySQL Better at GitHub (the GitHub blog)