I have posted results for FusionIO 320GB MLC on our ssdperformanceblog.com blog. To not duplicate content, there is link on original post:http://www.ssdperformanceblog.com/2011/06/fusionio-320gb-mlc-random-write-performance/ Follow my twitter Follow @VadimTk for further results.
InnoDB compression woes
May 20, 2011 By 14 Comments
InnoDB compression is getting some traction, and I see quite contradictory opinions. Someone has successful deployments in productions, and someone says that compression in current implementation is useless. To get some initial impression about performance I decided to run some sysbench with multi-tables benchmarks. I actually was preparing to do complex research, but even first [...]
Effect from innodb log block size 4096 bytes
January 3, 2011 By 19 Comments
In my post MySQL 5.5.8 and Percona Server: being adaptive I mentioned that I used innodb-log-block-size=4096 in Percona Server to get better throughput, but later Dimitri in his article MySQL Performance: Analyzing Percona’s TPCC-like Workload on MySQL 5.5 sounded doubt that it really makes sense. Here us quote from his article: “Question: what is a [...]
MySQL 5.5.8 and Percona Server: being adaptive
December 20, 2010 By 25 Comments
As we can see, MySQL 5.5.8 comes with great improvements and scalability fixes. Adding up all the new features, you have a great release. However, there is one area I want to touch on in this post. At Percona, we consider it important not only to have the best peak performance, but also stable and predictable performance. I refer you [...]
Write performance on Virident tachIOn card
December 13, 2010 By 10 Comments
This is crosspost from http://www.ssdperformanceblog.com/. Disclaimer: The benchmarks were done as part of our consulting practice, but this post is totally independent and fully reflects our opinion. One of the biggest problems with solid state drives is that write performance may drop significantly with decreasing free space. I wrote about this before (http://www.ssdperformanceblog.com/2010/07/free-space-and-write-performance/), using a [...]
Is there benefit from having more memory ?
November 19, 2010 By 10 Comments
My post back in April, http://www.mysqlperformanceblog.com/2010/04/08/fast-ssd-or-more-memory/, caused quite interest, especially on topic SSD vs Memory. That time I used fairy small dataset, so it caused more questions, like, should we have more then 128GB of memory? If we use fast solid state drive, should we still be looking to increase memory, or that configuration provides [...]
HandlerSocket on SSD
November 2, 2010 By 9 Comments
We all enjoyed Yoshinori announcement of HandlerSocket, the plugin to MySQL which open NOSQL way to access data stored in InnoDB. The published results are impressive, but I want to understand some, that’s why I run couple more experiments. In blog post Yoshinori used the case when all data fits into memory, and one of [...]
Percona Server scalability on multi-cores server
September 29, 2010 By 14 Comments
We now have hardware in our test lab that represents the next generation of commodity servers for databases. It’s a Cisco UCS C250 server, powered by two Intel Westmere CPUs (X5670 @ 2.93GHz). Each CPU has 6 cores and 12 threads. The most amazing part is the amount of memory. It has 384GB of RAM, which is [...]
SLC vs MLC
July 14, 2010 By Leave a Comment
(cross posting from SSDPeformanceBlog.com ) All modern solid state drives use NAND memory based on SLC (single level cell) or MLC (multi level cell) technologies. Not going into physical details – SLC basically stores 1 bit of information, while MLC can do more. Most popular option for MLC is 2 bit, and there is movement [...]
MySQL 5.5.4 in tpcc-like workload
April 21, 2010 By 25 Comments
MySQL-5.5.4 ® is the great release with performance improvements, let’s see how it performs in tpcc-like workload. The full details are on Wiki page http://www.percona.com/docs/wiki/benchmark:mysql:554-tpcc:start I took MySQL-5.5.4 with InnoDB-1.1, tpcc-mysql benchmark with 200W ( about 18GB worth of data), InnoDB log files are 3.8GB size, and run with different buffer pools from 20GB to [...]
