(转)Mysql 官方Memcached 插件初步试用感受 .
?
这些策略里，都有四个选项：innodb_only, cache_only, caching 和disabled。?
??? innodb_only: 数据直接存入innodb engine 中?
??? cache_only: 如同传统的memcache server，数据只存在memory 中?
??? caching: memory 中缓存，如果找不到，再向innodb engine 中搜索?
三、测试?
不管如何，我们还是需要看看它的性能如何，因时间有限，我只进行了一点简单测试，采用memslap 来进行，同时部署了一个官方的memcached server 来进行对比。?
首先是官方memcached server 数据：?
Get Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 3226683????? 37960??????? 39.6?????? 0????????? 25?????? 41149????? 374??????? 233.02???? 295.70?
Set Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 358528?????? 4217???????? 4.4??????? 0????????? 29?????? 41313????? 406??????? 233.22???? 335.51?
Total Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 3585210????? 42178??????? 44.0?????? 0????????? 25?????? 41313????? 377??????? 233.56???? 299.46?
然后是采用Innodb_only 策略的mysql memcached：?
Get Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 1043059????? 12271??????? 10.9?????? 0????????? 46?????? 395949???? 1026?????? 4794.93??? 424.72?
Set Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 115903?????? 1363???????? 1.2??????? 0????????? 76?????? 395981???? 2482?????? 9260.01??? 651.46?
Total Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 1158962????? 13634??????? 12.1?????? 0????????? 46?????? 395981???? 1172?????? 5427.44??? 443.28?
采用Caching 策略后的结果：?
Get Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 1101521????? 12959??????? 10.7?????? 0????????? 46?????? 126892???? 987??????? 3506.08??? 450.86?
Set Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 122398?????? 1439???????? 1.2??????? 0????????? 74?????? 126725???? 2211?????? 6591.01??? 683.18?
Total Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 1223919????? 14399??????? 11.9?????? 0????????? 46?????? 126892???? 1109?????? 3942.50??? 469.99?
最后，是cache_only 策略的结果：?
Get Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 1043059????? 12271??????? 10.9?????? 0????????? 46?????? 395949???? 1026?????? 4794.93??? 424.72?
Set Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 115903?????? 1363???????? 1.2??????? 0????????? 76?????? 395981???? 2482?????? 9260.01??? 651.46?
Total Statistics?
Type???? Time(s)? Ops????????? TPS(ops/s)?? Net(M/s)?? Get_miss?? Min(us)? Max(us)??? Avg(us)??? Std_dev??? Geo_dist??
Global?? 85?????? 1158962????? 13634??????? 12.1?????? 0????????? 46?????? 395981???? 1172?????? 5427.44??? 443.28?
四、结论?
从上述测试结果中可以看出，mysql 官方的解决方案，现在还是一个不怎么成熟的产品，尤其表现在不论读写，都不是太稳定，std_dev 和geo_dist 数值都非常大。性能方面，和memcached server 比起来，差了三倍以上，不过，在特殊场合，这种性能消耗还是可以接受的。由于时间有限，也没法再拿HandlerSocket 和这个比较一下了，感兴趣的同学可以帮忙做个比较。?
不过，不管怎样，mysql 社区至少看到了nosql 方面的强烈需求，并且有意愿在这上面有些表现，至少来说是个可喜的迹象。?
五、进阶、参考?
除了初步的使用外，在labs 里，还有mysql-cluster 解决方案，能够和此共同使用，构建稳固的storage system。?
另外，有关这个的各种说明、设计思路等，直接去其官网看吧，这里就不一一搬运了，地址：?
http://dev.mysql.com/tech-resources/articles/nosql-to-mysql-with-memcached.html?
http://blogs.innodb.com/wp/2011/04/nosql-to-innodb-with-memcached/?
http://blogs.innodb.com/wp/2011/04/get-started-with-innodb-memcached-daemon-plugin
?
?
?
?
