Some time ago, I published the article on AWS Aurora Benchmarking (AWS Aurora Benchmarking – Blast or Splash?), in which I analyzed the behavior of different solutions using synchronous replication in AWS environment. This blog follows up with some of the comments and suggestions I received regarding that post from the community and Amazon […]Read more
In this blog post, we’ll discuss how to benchmark MongoDB with sysbench.
In an earlier post, I mentioned our use of sysbench-mongodb (via this fork) to run benchmarks of MongoDB servers. I now want to share our work extending sysbench to make it work with MongoDB.
If you’re not familiar with sysbench, it’s a great project developed by Alexey […]
MySQL’s innodb_file_per_table is a wonderful thing – most of the time. Having every table use its own .ibd file allows you to easily reclaim space when dropping or truncating tables. But in some use cases, it may cause significant performance issues.
Many of you in the audience are responsible for running automated tests on your […]
The other day a customer asked me to do capacity planning for their web server farm. I was looking at the CPU graph for one of the web servers that had Hyper-threading switched ON and thought to myself: “This must be quite a misleading graph – it shows 30% CPU usage. It can’t really […]Read more
UPDATE: Since the publication of this blog post, the first release candidate of TokuMXse was made available for testing. Learn more about v1.0.0.RC.0. In addition, MongoDB has decided to call the release formerly known as v2.8, v3.0.
We’ve been working on TokuMXse for quite some time now. TokuMXse is the MongoDB 2.8 storage engine version of TokuMX that […]
The MySQL 5.6 Release has introduced some changes to how two phase commit works and is managed. In particular, the commit phase of transactions to the binary log is now serialized and this behavior is something we identified fairly immediately. We implement a group commit algorithm that needed to be altered so that TokuDB’s […]Read more
TokuDB offers high throughput for write intensive applications, and the throughput scales with the number of concurrent clients. However, when the binary log is turned on, TokuDB 7.5.2 throughput suffers. The throughput scaling problem is caused by a poor interaction between the binary log group commit algorithm in MySQL 5.6 and the way TokuDB […]Read more
In a few weeks I’m presenting “Performance Benchmarking: Tips, Tricks, and Lessons Learned” at Percona Live London 2014 (November 3-4). I continue to learn lessons and improve my benchmarking capabilities, so the content is a full upgrade from my presentation at Percona Live Santa Clara in April 2013. Anyone interested in achieving and sustaining […]Read more
Coming in TokuMX v2.0 is a feature we’re calling “Fast Updates”. Fast updates permit certain update operations to bypass the read-modify-write behavior that most databases require (including MongoDB and the current release of TokuMX). In this blog I’ll cover how Fast Updates work by describing a simple schema and workload, plus I’ll measure the […]Read more
New to TokuDB® v7.5 is a feature we’re calling “Read Free Replication” (RFR). RFR allows TokuDB replication slaves to process insert, update, and delete statements with almost no read IO. As a result, the slave can easily keep up with the master (no lag) as well as brings all the read IO capacity of […]Read more