750,000+ qps on a commodity MySQL/InnoDB 5.1 server

Like many other high scale web sites, we at DeNA(*) had similar issues for years. But we reached a different conclusion. We are using "only MySQL". We still use memcached for front-end caching (i.e. preprocessed HTML, count/summary info), but we do not use memcached for caching rows. We do not use NoSQL, either. Why? Because we could get much better performance from MySQL than from other NoSQL products. In our benchmarks, we could get 750,000+ qps on a commodity MySQL/InnoDB 5.1 server from remote web clients. We also have got excellent performance on production environments.
Maybe you can't believe the numbers, but this is a real story. In this long blog post, I'd like to share our experiences.
(*) For those who do not know.. I left Oracle in August 2010. Now I work at DeNA, one of the largest social game platform providers in Japan.
http://yoshinorimatsunobu.blogspot.com/2010/10/using-mysql-as-nosql-sto…

( zamboriz v | 2010. 11. 06., szo – 20:36 )

MySQL via HandlerSocket could get over 7.5 times higher throughput than traditional MySQL via SQL statements, even though %us was 3/4. This shows that SQL-layer in MySQL is very costly and skipping the layer certainly improves performance dramatically. It is also interesting that MySQL via HandlerSocket was 178% faster than memcached, and memcached spent too much %system resources.

( turul16 v | 2010. 11. 07., v – 07:00 )

Nagyon erdekes, prepered statemantekel merve meg elfert volna a cikben.

Amit nem lehet megirni assemblyben, azt nem lehet megirni.