Handler-SocketPluginforMySQL-SQL and NoSQL Performance

I remember that I wrote MySQLvsNoSQL more than half a year ago, and I have always insisted on using a database to store KV data, because it not only guarantees data security, it is mainly found that the qps of most systems is not that high at all, and the level of 4 K is very small, which MySQL can fully meet, because the optimized KV request can be implemented on the MySQL SQL layer.

I remember writing MySQL vs NoSQL more than half a year ago, and I have always insisted on using a database to store K/V data, because it not only guarantees data security, it is mainly found that the qps of most systems is not that high at all, and the level of 4 K performance is very small. This MySQL can fully meet, because the optimized K/V Request, it can be implemented at the SQL layer of MySQL.

I remember writing MySQL vs NoSQL more than half a year ago, and I have always insisted on using a database to store K/V data, because it not only guarantees data security, it is mainly found that the qps of most systems is not that high at all, and the level of 4 K performance is very small. This MySQL can fully meet, because the optimized K/V Request, at the SQL layer of MySQL, the qps of each core is about 5 kb, which is greatly improved after HandlerSocket is released.

HandlerSocket plugin for MySQL has been out for some time. Given the robustness and security of HandlerSocket and InnoDB, it is foreseeable that HandlerSocket replaces NoSQL storage/Cache such as Memcached, which is the trend of the times.

HandlerSocket is a plug-in of MySQL. It is used to skip the SQL layer of MySQL and directly access the internal InnoDB Storage engine to give full play to the performance advantages of InnoDB. In addition, the ACID feature of InnoDB, this ensures data security.

The HandlerSocket Plugin for MySQL performance is similar to that of Memcached. the test data in the original article is better than that of Memcached. Next, we prepare to compare and test the ndbapi performance to provide a reference for the system architecture.

                           approx qps     server CPU utilMySQL via SQL                105,000      %us 60%  %sy 28%memcached                    420,000      %us  8%  %sy 88%MySQL via HandlerSocket      750,000      %us 45%  %sy 53%

HandlerSocket Source Code address: https://github.com/ahiguti/HandlerSocket-Plugin-for-MySQL/

HandlerSocket client:

HandlerSocket Client for Perl

HandlerSocket Client for Python

HandlerSocket Client for PHP

HandlerSocket Client for Java

--------------
Update: 2011/04/08
In Dell R710 dual-core E5620, mysql version 5.1.54, without any source code modification, using the php handler-socket extension, the test results are stable at 0.33 million + QPS, the cpu usage of mysqld is about 50%.

Related posts:

1. From NoSQL to MySQL + Memcache (d) Heavy-tree MySQL
2. MySQL vs NoSQL efficiency and cost competition
3. InnoDB Plugin 1.0.4 for MySQL 5.1.37
4. InnoDB plugin 1.0.7
5. Memcached and MySQL

? Tan junqing published a study on MySQL performance, MySQL Cluster, and MySQL HA High Availability-MySQL laboratory, 2010.
The source and author information of an article can be reproduced at will.
Link: http://www.mysqlab.net/blog/2010/11/handler-socket-plugin-for-mysql/

Tags: HandlerSocket, NoSQL