Shulou(Shulou.com)05/31 Report--

This article will explain in detail why MySQL does not recommend using UUID as the innodb primary key. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

1) .UUID can guarantee the uniqueness of ID, but it can not meet many other characteristics needed by business systems, such as rough ordering of time, reversibility and manufacturability.

2). UUID is generated with complete time data, and its performance is relatively poor.

3) .UUID is relatively long, which takes up a lot of space, which indirectly leads to the decline of database performance.

4) .UUID is not ordered, which will cause too many random writes in the B + tree index (consecutive ID will produce partial sequential writes)

5)。 The orderly append operation cannot be produced when writing, but the insert operation is needed. The entire B+ tree node will be read into memory, and after inserting this record, the entire node will be written back to disk. When the record takes up a large amount of space, the performance will be significantly degraded.

6). UUID is not growing sequentially at present, as a result of primary key writing, random IO is serious.

This is the end of this article on why MySQL does not recommend using UUID as the innodb primary key. I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it out for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.