how innodb lost its advantage
For years it was very easy to defend InnoDB’s advantage over competition – covering index reads were saving I/O operations and CPU everywhere, table space and I/O management allowed to focus on database and not on file systems or virtual memory behaviors, and for past few years InnoDB compression was the way to have highly efficient OLTP (or in our case – SGTP – Social Graph Transaction Processing
on swapping and kernels
There is much more to write about all the work we do at Facebook with memory management efficiency on our systems, but there was this one detour investigation in the middle of 2012 that I had to revisit recently courtesy of Wikipedia. There are lots of factors that make machines page out memory segments into disk, thus slowing everything down and locking software up – from file system cache pressu
how MySQL engineering broke the backups
MySQL has exceptional track of record by introducing minor fixes that cause major breakages. Though usually I could blame naiveté of engineers, who did not really ever have to deal with production implications, but lately I can start sensing various business implications against open-source offerings. As an original author of mydumper I really cannot get out of my mind that 5.5 and 5.6 metadata lo
on nuodb and falcon
Warning: this is a mixture of historical content, biases, stupid marketing and unknown/proprietary/closed source technologies. Proceed with caution. NuoDB marketing was sending out this message, encouraging me to blog (they were looking for bloggers too): And while Facebook sharded MySQL 4000 times, even they call it a “fate worse than death.” We’ve seen this phrase before and it did not come from
MySQL is bazillion times faster than MemSQL
I don’t like stupid benchmarks, as they waste my time. I don’t like stupid marketing, as it wastes my time too. Sometimes I succumb to those things, and now in return I want to waste your time a bit. So, this MemSQL thing, written by some smart guys has been making rounds in press and technical community. Centerpiece of all the communication was: “MemSQL, the database they have developed over the
MySQL metrics for read workloads
There are multiple metrics that are really useful for read workload analysis, that should all be tracked and looked at in performance-critical environments. The most commonly used is of course Questions (or ‘Queries’, ‘COM_Select’) – this is probably primary finger-pointing metric that can be used in communication with different departments (“why did your qps go up by 30%?”) – it doesn’t always re
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
