Today we glad to announce release 1.0.3-4 of our XtraDB storage engine.
Here is a list of enhancements in this release:
Many InnoDB scalability problems seem fixed in InnoDB-plugin-1.0.3 and I expect InnoDB-plugin will run fine on 16-24 cores boxes for many workloads. And now it is time to look on systems with 32GB+ of RAM which are not rare nowadays. Working with real customer systems I have wish-list of features I would like to see soon:
One little bit of wisdom I would like to pass on:
If a program runs fast with 20 threads, that does not mean it
will run fast with 50. And if it runs fast with 50, it does not
mean that it will run fast with 100, and if it runs fast with 100
... don't bet on it running fast with 200 :)
In my last blog I discussed some improvement to the
performance of PBXT running the DBT2 benchmark. Despite the
overall significant increase in performance I noted a drop off at
32 threads that indicated a scaling problem. For the last couple
of weeks I have been working on this problem and I have managed
to fix it:
As before, this test was done using MySQL
5.1.30 on an 8 core, 64-bit, Linux machine with an SSD drive and
a 5 warehouse DBT2 …
We had this plan.
We were going to show off the latest Innodb
plugin.
We imported into the tree... got a benchmark and then...
We found a race condition in our code that showed up once we
added the new plugin to our code.
Is the plugin faster?
Sure seems to be... but make up your own mind.
You can play with it here: https://edge.launchpad.net/drizzle/trunk/2009.03.962
(which includes Solaris/Sparc support now)
Curious about the numbers? Below is a current run of sysbench
from one of our 16core systems. Very soon now Jay will have the
public regression system available.
What will it do? Anyone who wants to follow our efforts on
performance will be able too.
Want to …
When I wrote my previous post titled all about storedconfigs, I was pretty confident I explained everything I could about storedconfigs… I was wrong of course
A couple of days ago, I was helping some USG admins who were facing an interesting issue. Interesting for me, but I don’t think they’d share my views on this, as their servers were melting down under the database load.
But first let me explain the issue.
The issue
The thing is that when a client checks in to get its configuration, the puppetmaster compiles its configuration to a digestible format and returns it. This operation is the process of transforming the AST built by parsing the …
[Read more]It's always fun when you come into work and notice that one of your database monitors/graphs has changed from showing almost no row accesses/sec to 40,000 rows/sec in a matter of minutes. And then by lunch time they are showing 90,000 rows/sec. What's up with that?MySQL Enterprise Monitor Row Accesses:Well, of course the first thing you do is check all your cacti monitors, because there is
The MySQL marketplace today is far more complex then simply
choosing between a particular version of MySQL that Sun/MySQL produces.
The MySQL server product in general is released under the
GNU General Public License (GPL) v2, however
you should carefully review the MySQL Legal
Policies as a number of exceptions and different license
agreements operate for companion tools such as MySQL Cluster,
MySQL client libraries and documentation for example.
Looking into the MySQL ecosystem for products, I’ve produced the following categories:
DBT2, with over 40% conflicts, is an very challenging benchmark,
especially for an MVCC based engine. And, as a result, it is not
a test that an engine is automatically good at. InnoDB has been
extensively optimized for DBT2, and it shows.
For the last few weeks I have had the opportunity to focus on
PBXT DBT2 performance for the first time. I started with a memory
bound DBT2 test and the current state of this work is illustrated
below.
These results were achieved using MySQL 5.1.30 on
an 8 core, 64-bit, Linux machine with an SSD drive and a 5
warehouse DBT2 database.
The dip off at 32 threads is left as an exercise for the reader
:) Patches will be excepted!
So what were the major changes that lead to this
improvement?
Don't Wait Too Long!
When I began the optimizations, PBXT …
Here are some common performance tuning concepts that I frequently run into. Please note that this really is only a basic introduction to performance tuning. For more in-depth tuning, it strongly depends on your systems, data and usage.
Server Variables
For tuning InnoDB performance, your primary variable is innodb_buffer_pool_size. This is the chunk of memory that InnoDB uses for caching data, indexes and various pieces of information about your database. The bigger, the better. If you can cache all of your data in memory, you’ll see significant performance improvements.
For MyISAM, there is a similar buffer defined by key_buffer_size, though this is only used for indexes, not data. Again, the bigger, the better.
Other variables that are worth investigating for performance tuning are:
query_cache_size - This can be very useful if you have a small number of read queries that are repeated frequently, …
[Read more]We finally managed to get Intel X25-E SSD drive into our lab. I attached it to our Dell PowerEdge R900. The story making it running is worth separate mentioning - along with Intel X25-E I got HighPoint 2300 controller and CentOS 5.2 just could not start with two RAID controllers (Perc/6i and HighPoint 2300). The problem was solved by installing Ubuntu 8.10 which is currently running all this system. Originally I wanted to publish some nice benchmarks where InnoDB on SSD outperforms RAID 10, but recently I faced issue which can make previous results inconsistent.
In short words using Intel SSD X25-E card with enabled
write-cache (which is default and most performance mode) does not
warranty storing all InnoDB transactions on permanent
storage.
I am having some déjà vu here, as Peter was rolling this 5 years
ago http://lkml.org/lkml/2004/3/17/188 regarding
regular IDE …
