… also promised more low concurrency SSB tests when Peter blogged about the importance of performance at low concurrency. The SSB The SSB… and InnoDB may perform differently under concurrency, which this benchmark does not cover. I will make a follow-up post about concurrency in another blog post in this series. Regardless, when the working set fits in memory, InnoDB almost always…
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
… calloc() directly instead of using InnoDB heap allocation. This may improve write performance for high levels of concurrency. Bug fixed #1185686. Under… if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040. The INNODB_CHANGED_PAGES table couldn’t be queried if the log…
Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available
April 17, 2013 By 2 Comments
…. Bug fixed #1154095 (Alex Yurchenko). If variable innodb_thread_concurrency has been defined to throttle InnoDB access, and work load contained DDL statements… adding a new method to cancel a thread waiting for InnoDB concurrency. Bug fixed #1155183 (Seppo Jaakola). Handling of the network issues…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
… transactions, start suffering from the trx_list overhead created by concurrent updates. Once we step away from this spherical read-only… it doesn’t help much, because e.g. for 1024 concurrent threads each SELECT has to scan about 100 update transactions…_commit = 2 innodb_flush_method = O_DIRECT innodb_log_buffer_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 2000M innodb_log_files…
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
April 12, 2013 By 3 Comments
… of MySQL performance that still stands in the way of InnoDB scalability is the trx_list scan on consistent read view… scan in MySQL 5.5 basically kills throughput on high concurrency. The picture changes dramatically when the read-only optimization in… list scan and it provides stable throughput even at 4096 concurrent connections. So both the general “trx descriptors” optimization introduced in…
Comment: Benchmarking Percona Server TokuDB vs InnoDB
May 8, 2013 By 32 Comments
…) What concurrency did you use for the INSERT test? Don’t know if TokuDB handle concurrent workload as well as InnoDB 2) Can… a secondary index? I heard that TokuDB is slower than InnoDB on SELECT but it’d be interesting to see by…
Post: Is Synchronous Replication right for your app?
May 14, 2013 By 18 Comments
… applying Callaghan’s law to single-server Innodb, we’d get: [On a single node Innodb server] a given row can’t… both of the above examples you can imagine plenty of concurrent clients attempting to modify the same record at once. But… your hotspots were really bad in standalone Innodb, you might consider relaxing the fsync: set innodb_flush_log_at_trx_commit to…
Post: 10 years of MySQL User Conferences
April 11, 2013 By 6 Comments
… API diminishing importance of the Innodb storage engine. The Falcon storage engine was announced as a potential Innodb successor. A “MySQL Network… will be separate from MySQL Server, providing a more scalable Innodb version with more features. Gearman and MemcacheD storage engine plugins… as a free event going concurrently with the conference and announced Percona XtraDB as improved and extended Innodb Plugin version, MySQL 5…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the event… #1041981 (Alexey Bychko). Fixed the upstream bug #68197 that caused InnoDB to misclassify internal read operations as synchronous when they were…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the event… #1041981 (Alexey Bychko). Fixed the upstream bug #68197 that caused InnoDB to misclassify internal read operations as synchronous when they were…
