We just pushed to sysbench support for workload against multiple tables ( traditionally it used only single table).
It is available from launchpad source tree lp:sysbench .
This is set of LUA scripts for sysbench 0.5 ( it supports scripting), and it works following way:
- you should use --test=tests/db/oltp.lua to run OLTP test
i.e. prepare ./sysbench --test=tests/db/oltp.lua --oltp-tables-count=25 prepare
run: ./sysbench --test=tests/db/oltp.lua --oltp-tables-count=25 --num-threads=5 run
- MySQL Performance Blog: InnoDB compression woes
- High Scalability: VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
- Trevor Turk: Weekly Digest, 5-29-10
- Axon Flux // A Ruby on Rails Blog: Impressive tech talk on Scaling MySQL at Facebook
- igvita.com: Future of RDBMS is RAM Clouds & SSD
- How Software is Built: Interiew with Denis Lussier - Co-Founder - CTO - EnterpriseDB
As continuation of my CPU benchmarks it is interesting to see what is scalability limitation in MySQL 5.6.2, and I am going to check that using PERFORMANCE SCHEMA, but before that let's estimate what is potential overhead of using PERFORMANCE SCHEMA. So I am going to run the same benchmarks (sysbench read-only and read-write) as in previous post with different performance schema options and compare results.
I am going to use Cisco UCS C250
with next settings:
PERFORMANCE SCHEMA disabled (NO PS)
Having two big boxes in our lab, one based Intel Nehalem ( Cisco UCS C250 ) and second on AMD Opteron ( Dell PowerEdge R815 ), I decided to run some simple sysbench benchmark to compare how both CPUs perform and what kind of scalability we can expect.
It is hard to make apples to apples comparison, but I think it is still interesting.
Cisco UCS C250 has total 12 cores / 24 threads of Intel Nehalem X5670, and Dell PowerEdge R815 has 48 cores of AMD Opteron 6168.
- MySQL Performance Blog: Performance Schema overhead
- Signal vs. Noise: Nuts & Bolts: Database Servers
- interblah.net: road-testing-the-eleven-inch-air
- Zen and the Art of Programming: IBM releases DB2 Express-C 9.7.2
- terrbear.org: Guidification
- How Software is Built: Interview with Rich Wolski - Eucalyptus CTO
It is well known fact that InnoDB standard page size is 16K or 16384 bytes. Sometime ago we added feature to Percona Server to change that to 4K or 8K ( innodb_page_size ). That maybe useful for SSD that operates with 4K blocks and you can get really much better throughput with 4K ( however we need to run benchmarks yet to see real effect from it).
The bigger limitation is that this setting is for whole database instance and you need to mysqldump your data, re-create database and load data.
- Giles Bowkett: Internet Marketing Video, Version 2
- Vineet Gupta | Computer Programmer: Key I/O Changes in Windows Vista
- Opscode Blog: Back to Back! Chef 0.7.2 and Chef 0.7.4 released.
- World Wide Webber: WS-REST 2011 Call for Papers
Previously we had XtraBackup Windows binaries for 1.0 and 1.2 releases, and they were based on Cygwin compilation of MySQL.
After MySQL 5.5 moved to CMake, and cygwin compilation is not supported anymore, it took some efforts for us to come up with native Windows builds, but they are there already. We consider them "alpha" quality, as there some know limitations,
but you should be able to make backup and restore from it. If you are interested in Windows backup I encourage …
- MySQL Performance Blog: Percona Server and XtraBackup Weekly News, April 25th
- Dr Nic: Making CI easier to do than not to with Hudson CI and Vagrant
- carpeaqua by Justin Williams: My 2010 Ultimate Developer and Power Users Tool List for Mac OS X (2010 Edition)
- On the Path: Securing Memcache in 2 Minutes
- Global Nerdy: And So It Begins (or Frederic's Officially on Board)
- Oleksiy Kovyrin: Fwd: Scalexis Inc is Hiring
There were recent discussion about DROP TABLE performance in InnoDB,
you may check Peter's post http://www.mysqlperformanceblog.com/2011/02/03/performance-problem-with-innodb-and-drop-table/
and corresponding bugs: http://bugs.mysql.com/bug.php?id=51325 and http://bugs.mysql.com/bug.php?id=56332 .
It may not sound that serious, but if your workload often uses DROP TABLE and you have big buffer pool it may be significant issue. And this is getting especially …
- MySQL Performance Blog: Introducing new type of benchmark
- igvita.com: HandlerSocket: The NoSQL MySQL & Ruby
- Signal vs. Noise: Keeping your slave warm
- paperplanes: MongoDB, Data Durability and Improvements coming in 1.8
- Giles Bowkett: Facebook As National Security Issue
- Eddorre.com: Rails Ultimate Install Guide on OS X Snow Leopard (using RVM, Homebrew, and Passenger)
…helper script README-Solaris for building on Solaris. ( Vadim Tkachenko)
Changes were made to the post-install messages ( Ignacio Nin)
Bugs Fixed
Bug # 631667 - The mysql binary is now built with readline support so that command line browsing is possible. ( Ignacio Nin)
Bug # 716575 - When using the Expand Table Import feature, importing .ibd files smaller than 1 MB could lead to a server crash. ( Yasufumi Kinoshita)
Bug # 727704 - When …
Percona XtraBackup 1.6 is now available for download and is the current stable release version of XtraBackup.
Options Added
Added option --extra-lsndir to innobackupex . When specified for the backup phase, the option is passed to xtrabackup , and lsn information is stored with the file in the specified directory. This is needed so that lsn information is preserved during stream backup. ( Vadim Tkachenko)
Added option --incremental-lsn to innobackupex . If specified, this option …
- On the Path: Tuning MySQL
I mentioned problems with InnoDB flushing in a previous post .
Before getting to ideas on a solution, let's define some terms and take a look into theory.
The two most important parameters for InnoDB performance are innodb_buffer_pool_size and innodb_log_file_size .
InnoDB works with data in memory, and all changes to data are performed in memory. In order to survive a crash or system failure, InnoDB is logging changes into InnoDB transaction logs. The size of …
- MySQL Performance Blog: Disaster: MySQL 5.5 Flushing
- MySQL Performance Blog: The relationship between Innodb Log checkpointing and dirty Buffer pool pages
- Junior developer: Rails test data not getting rolled back
- oldmoe: 101 Reasons Why PostgreSQL is a better fit for Rails than MySQL
- High Scalability: Facebook at 13 Million Queries Per Second Recommends: Minimize Request Variance
- Pennysmalls: Much faster Rails tests if you use MyISAM
You may have seen in the last couple of weekly news posts that Baron mentioned we are working on a new adaptive flushing algorithm in InnoDB. In fact, we already have three such algorithms in Percona Server (reflex, estimate, keep_average). Why do we need one more? Okay, first let me start by showing the current problems, and then we will go to solutions.
The basic problem is that, unfortunately, none of the existing flushing implementations (including both MySQL native adaptive flushing …
- MySQL Performance Blog: Adaptive flushing in MySQL 5.6
- MySQL Performance Blog: InnoDB Flushing: Theory and solutions
- On the Path: Tuning MySQL
- JJinuxLand: MySQL: Disk Usage Can Never Shrink When Using InnoDB
- Rails Envy ยป Home: RailsLab: Scaling Your Database - Part 2
- Simple thoughts - articles: The Internal Storage Mechanism For Globalize for Rails Model Translations