サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
災害への備え
mysqlha.blogspot.com
Percona published Linkbench results. It looks like they set innodb_io_capacity to a large value but did not increase innodb_lru_scan_depth. I think that is a mistake. This is a mistake that I have made and that I hope you can avoid. innodb_io_capacity limits the number of pages flushed per second from the flush list. innodb_lru_scan_depth limits the number of pages flushed per second from the LRU
Someone I know used to make jokes about their plans to run MySQL 4.0 forever. It wasn't a horrible idea as 4.0 was very efficient and the Google patch added monitoring and crash-proof replication slaves. I spent time this week comparing MySQL 5.7.2 with 5.6.12 and 5.1.63. To finish the results I now have numbers for 4.1.22. I wanted to include 4.0 but I don't think it works good when compiled with
This isn't a new message but single-threaded performance continues to get worse in 5.7.2. There have been regressions from 5.1 to 5.6 and now to 5.7. I skipped testing 5.5. On the bright side there is progress on a bug I opened for this and MySQL seems to be very interested in making things better. The regressions for UPDATE and SELECT are much worse than for HANDLER so I assume the optimizer acco
I compared the performance of MySQL 5.6.11 versus 4.0.30 using a read-only workload with sysbench. Performance was much better for 5.6.11 in most cases. At low-concurrency MySQL 4.0 was a bit faster. MySQL 5.6.11 was faster at high-concurrency and when doing many page reads per second. The product has improved a lot since I started using MySQL. I followed most of my advice on building and configur
MySQL 5.6 has a new option for innodb_flush_method . When O_DIRECT_NO_FSYNC is used then fsync is not done after writes. This was a response...
I spent more time looking at the performance regressions in MySQL 5.6 for single-threaded read-only workloads and I can get 5.6 closer to 5...
I am trying to understand why a server would go from 0 to 45 and then back to 0 seconds of replication lag as reported by the Seconds_Behind...
This is the end of my public performance comparison of MongoDB versus MySQL, at least for the next few weeks. For these tests I used a 16-co...
This continues the silly benchmark series and compares performance from concurrent clients that fetch by secondary key. The previous post c...
This is yet another silly benchmark because the results are likely to be misused. The results probably do not matter to you. I like MongoDB....
A few years ago MySQL+memcached and PostgreSQL+memcached were the only choices for high-scale applications. That has changed with the arriva...
Managed MySQL is here. Amazon RDS allows you to run MySQL on their hardware. It isn't perfect, but I think this is a great first release. I...
Slides for my talks. Code described here is in the v3 Google patch .
MyISAM is faster because everyone says so. This has even made it to the MyISAM wikipedia entry . That is unfortunate because I think that I...
There may be a simple way to improve InnoDB performance on SMP servers. The benefit is not as great as that obtained by using the smpfix fro...
Stop reading now if you don't like handwaving. I have taken the Tokutek challenge and run iibench. This test matches behavior that occasio...
Q4M is a new storage engine that supports persistent queues. For a project that claims to have been started in December 2007, the code and ...
このページを最初にブックマークしてみませんか?
『High Availability MySQL』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く