Benchmarking 主鍵字段的三種存儲方式

events_uuid – UUID binary(16) PRIMARY KEY

events_int – 自增序列bigint(20) NOT NULL AUTO_INCREMENT,

events_uuid_ordered – Rearranged UUID binary(16) as PRIMARY KEY

I created three stored procedures which insert 25K random rows at a time into the respective tables. There are three more stored procedures which call the random insert-stored procedures in a loop and also calculate the time taken to insert 25K rows and data and index size after each loop. Totally I have inserted 25M records.

###1.數(shù)據(jù)大小

Data Size Horizontal Axis – Number of inserts x 25,000 Vertical Axis – Data Size in MB The data size for UUID table is more than other two tables.

###2.索引大小 Index Size Horizontal axis – Number of inserts x 25,000 Vertical axis – Index Size in MB

###3.總大小 Horizontal Axis – Number of inserts x 25,000 Vertical Axis – Total Size in MB

###4.時間Time taken Horizontal axis – Number of inserts x 25,000 Vertical axis – Time Taken in seconds

參考https://www.percona.com/blog/2014/12/19/store-uuid-optimized-way/

總結(jié)

以上是生活随笔為你收集整理的mysql uuid 性能_mysql InnoDB UUID 主键 性能优化【性能分析篇】.md的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。