Home Database Mysql Tutorial Detailed process of comparing the advantages and disadvantages of MySQL using auto-incrementing ID primary key and UUID as primary key (500W single table)

Detailed process of comparing the advantages and disadvantages of MySQL using auto-incrementing ID primary key and UUID as primary key (500W single table)

Feb 16, 2017 am 11:37 AM

Reason for testing

A development colleague made a framework in which the primary key is uuid. I suggested to him that mysql should not use uuid and use auto-incrementing primary keys. Auto-incrementing primary keys are more efficient. He said it is not necessarily high. I said innodb’s index The feature has led to the most efficient use of auto-incrementing ID as the primary key. In order to convince him, I prepared to do a detailed test.

As an Internet company, there must be a user table, and the user table UC_USER basically has millions of records. Therefore, the test is carried out based on the quasi-test data based on this table.

The approximate environment is: Centos6.5, MySQL5.6.12

1, Prepare tables and data

UC_USER, auto-increment ID as primary key:

UC_USER_PK_VARCHAR table, string ID is the primary key, using uuid

##CREATE TABLE `UC_USER` (


`ID` bigint(20) NOT NULL AUTO_INCREMENT COMMENT 'Primary Key', `USER_NAME` varchar(100) DEFAULT NULL COMMENT 'Username',
`USER_PWD` varchar(200) DEFAULT NULL COMMENT 'Password',
`BIRTHDAY` datetime DEFAULT NULL COMMENT 'Birthday',
`NAME` varchar(200) DEFAULT NULL COMMENT 'Name',
`USER_ICON` varchar(500) DEFAULT NULL COMMENT 'Avatar picture',
`SEX` char(1 ) DEFAULT NULL COMMENT 'Gender, 1: Male, 2: Female, 3: Confidential',
`NICKNAME` varchar(200) DEFAULT NULL COMMENT 'Nickname',
`STAT` varchar(10) DEFAULT NULL COMMENT 'User status, 01: normal, 02: frozen',
`USER_MALL` bigint(20) DEFAULT NULL COMMENT 'Current MALL',
`LAST_LOGIN_DATE` datetime DEFAULT NULL COMMENT 'Last login time',
`LAST_LOGIN_IP` varchar(100) DEFAULT NULL COMMENT 'Last login IP',
`SRC_OPEN_USER_ID` bigint(20) DEFAULT NULL COMMENT 'Source of joint login',
`EMAIL` varchar(200) DEFAULT NULL COMMENT 'Mailbox',
`MOBILE` varchar(50) DEFAULT NULL COMMENT 'Mobile phone',
`IS_DEL` char(1) DEFAULT '0' COMMENT 'Whether to delete',
`IS_EMAIL_CONFIRMED` char(1 ) DEFAULT '0' COMMENT 'Whether to bind an email',
`IS_PHONE_CONFIRMED` char(1) DEFAULT '0' COMMENT 'Whether to bind a mobile phone',
`CREATER` bigint(20) DEFAULT NULL COMMENT 'Create People',
`CREATE_DATE` datetime DEFAULT CURRENT_TIMESTAMP COMMENT 'Registration time',
`UPDATE_DATE` datetime DEFAULT CURRENT_TIMESTAMP COMMENT 'Modification date',
`PWD_INTENSITY` char(1) DEFAULT NULL COMMENT 'Password strength' ,
`MOBILE_TGC` char(64) DEFAULT NULL COMMENT 'Mobile phone login ID',
`MAC` char(64) DEFAULT NULL COMMENT 'mac address',
`SOURCE` char(1) DEFAULT ' 0' COMMENT '1:WEB,2:IOS,3:ANDROID,4:WIFI,5:Management system, 0:Unknown',
`ACTIVATE` char(1) DEFAULT '1' COMMENT 'Activate, 1: Activation, 0: Not activated',
`ACTIVATE_TYPE` char(1) DEFAULT '0' COMMENT 'Activation type, 0: automatic, 1: manual',
PRIMARY KEY (`ID`),
UNIQUE KEY `USER_NAME` (`USER_NAME`),
KEY `MOBILE` (`MOBILE`),
KEY `IDX_MOBILE_TGC` (`MOBILE_TGC`,`ID`),
KEY `IDX_EMAIL` (` EMAIL`,`ID`),
KEY `IDX_CREATE_DATE` (`CREATE_DATE`,`ID`),
KEY `IDX_UPDATE_DATE` (`UPDATE_DATE`)
) ENGINE=InnoDB AUTO_INCREMENT=7122681 DEFAULT CHARSET= utf8 COMMENT='User Table'

CREATE TABLE `UC_USER_PK_VARCHAR_1` (
`ID` varchar(36) CHARACTER SET utf8mb4 NOT NULL DEFAULT '0' COMMENT 'Primary Key' ,
`USER_NAME` varchar(100) DEFAULT NULL COMMENT 'Username',
`USER_PWD` varchar(200) DEFAULT NULL COMMENT 'Password',
`BIRTHDAY` datetime DEFAULT NULL COMMENT ' Birthday',
`NAME` varchar(200) DEFAULT NULL COMMENT 'Name',
`USER_ICON` varchar(500) DEFAULT NULL COMMENT 'Avatar picture',
`SEX` char(1) DEFAULT NULL COMMENT 'Gender, 1: Male, 2: Female, 3: Confidential',
`NICKNAME` varchar(200) DEFAULT NULL COMMENT 'Nickname',
`STAT` varchar(10) DEFAULT NULL COMMENT 'User status , 01: Normal, 02: Freeze',
`USER_MALL` bigint(20) DEFAULT NULL COMMENT 'Current MALL',
`LAST_LOGIN_DATE` datetime DEFAULT NULL COMMENT 'Last login time',
`LAST_LOGIN_IP `varchar(100) DEFAULT NULL COMMENT 'Last login IP',
`SRC_OPEN_USER_ID` bigint(20) DEFAULT NULL COMMENT 'Source of joint login',
`EMAIL` varchar(200) DEFAULT NULL COMMENT 'Mailbox' ,
`MOBILE` varchar(50) DEFAULT NULL COMMENT 'Mobile phone',
`IS_DEL` char(1) DEFAULT '0' COMMENT 'Whether to delete',
`IS_EMAIL_CONFIRMED` char(1) DEFAULT ' 0' COMMENT 'Whether to bind an email',
`IS_PHONE_CONFIRMED` char(1) DEFAULT '0' COMMENT 'Whether to bind a mobile phone',
`CREATER` bigint(20) DEFAULT NULL COMMENT 'Creator',
`CREATE_DATE` datetime DEFAULT CURRENT_TIMESTAMP COMMENT 'Registration time',
`UPDATE_DATE` datetime DEFAULT CURRENT_TIMESTAMP COMMENT 'Modification date',
`PWD_INTENSITY` char(1) DEFAULT NULL COMMENT 'Password strength',
`MOBILE_TGC` char(64) DEFAULT NULL COMMENT 'Mobile phone login ID',
`MAC` char(64) DEFAULT NULL COMMENT 'mac address',
`SOURCE` char(1) DEFAULT '0' COMMENT '1:WEB,2:IOS,3:ANDROID,4:WIFI,5:Management system, 0:Unknown',
`ACTIVATE` char(1) DEFAULT '1' COMMENT 'Activate, 1: Activate, 0 : Not activated',
`ACTIVATE_TYPE` char(1) DEFAULT '0' COMMENT 'Activation type, 0: automatic, 1: manual',
PRIMARY KEY (`ID`),
UNIQUE KEY ` USER_NAME` (`USER_NAME`),
KEY `MOBILE` (`MOBILE`),
KEY `IDX_MOBILE_TGC` (`MOBILE_TGC`,`ID`),
KEY `IDX_EMAIL` (`EMAIL`, `ID`),
KEY `IDX_CREATE_DATE` (`CREATE_DATE`,`ID`),
KEY `IDX_UPDATE_DATE` (`UPDATE_DATE`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='User table ';

2、500WData test

2.1 Enter 500W data, auto-increment ID Save half the disk Space

Determine the amount of data in the two tables

Table with auto-increment id as the primary key

mysql> select count(1) from UC_USER;

+----------+

| count(1) |

+----- -----+

| 5720112 |

+----------+

1 row in set (0.00 sec)

mysql>

# Table with uuid as primary key

mysql> select count(1) from UC_USER_PK_VARCHAR_1; #+----------+

| count(1) |

+----------+

| 5720112 |

+----------+

1 row in set (1.91 sec)

Judging from the space capacity occupied, the auto-increment ID is about half smaller than the UUID.

Auto-increment ID -rw-rw---- 1 mysql mysql 2.5G Aug 11 18:29 UC_USER.ibd2.5 GUUID-rw-rw---- 1 mysql mysql 5.4G Aug 15 15:11 UC_USER_PK_VARCHAR_1.ibd5.4 G
Primary key type

Data file size

Occupied capacity

2.2

Single data index query , the self-increment id and uuid are not much different

##SQL statementExecution time ( Seconds)Auto-increment IDSELECT SQL_NO_CACHE t .* FROM test.`UC_USER_PK_VARCHAR_1` t WHERE t.`MOBILE` ='14782121512';0.117SELECT SQL_NO_CACHE t.* FROM test.`UC_USER` t WHERE t.`MOBILE` IN( '14782121512','13761460105');SELECT SQL_NO_CACHE t.* FROM test.`UC_USER_PK_VARCHAR_1` t WHERE t.`MOBILE` IN ('14782121512','13761460105');##自increment IDSELECT SQL_NO_CACHE t.* FROM test.`UC_USER` t WHERE t.`CREATE_DATE`='2013-11-24 10:26:36' ;UUIDSELECT SQL_NO_CACHE t.* FROM test.`UC_USER_PK_VARCHAR_1` t WHERE t.`CREATE_DATE`='2013-11-24 10 :26:43' ;
Primary key type

##SELECT SQL_NO_CACHE t.* FROM test.`UC_USER` t WHERE t.`MOBILE` ='14782121512';

##0.118

##UUID

##Auto-increment ID

0.049

UUID

0.040

0.139

0.126

2.3 RangelikeQuery, self-incrementIDPerformance is better than UUID

##Auto-increment IDUUID (3) Range query 200 pieces of data, auto-increment ID performance is better than UUIDAuto-increment IDUUID Range query total quantity, auto-increment ID is better than UUIDAuto-increment IDUUID

##Primary key type

SQL statement

Execution time (seconds)

(1) Fuzzy range query 1000 pieces of data, auto-increment ID performance is better than UUID

Auto-increment ID

SELECT SQL_NO_CACHE t.* FROM test.`UC_USER` t WHERE t.`MOBILE` LIKE '147%' LIMIT 1000;

1.784

UUID

SELECT SQL_NO_CACHE t.* FROM test.`UC_USER_PK_VARCHAR_1` t WHERE t.`MOBILE` LIKE '147%' LIMIT 1000;

3.196

#(2) Query 20 pieces of data in the date range. The auto-increment ID is slightly weaker than UUID

SELECT SQL_NO_CACHE t.* FROM test.`UC_USER` t WHERE t.`CREATE_DATE` > '2016-08-01 10:26:36' ORDER BY t.`UPDATE_DATE` DESC LIMIT 20;

0.601

SELECT SQL_NO_CACHE t.* FROM test.`UC_USER_PK_VARCHAR_1` t WHERE t.`CREATE_DATE` > '2016-08-01 10:26:36' ORDER BY t.`UPDATE_DATE` DESC LIMIT 20;

0.543

SELECT SQL_NO_CACHE t.* FROM test.`UC_USER` t WHERE t.`CREATE_DATE` > '2016-07-01 10:26:36' ORDER BY t.`UPDATE_DATE` DESC LIMIT 200;

2.314

SELECT SQL_NO_CACHE t.* FROM test.`UC_USER_PK_VARCHAR_1` t WHERE t.`CREATE_DATE` > '2016-07-01 10:26:36' ORDER BY t.`UPDATE_DATE` DESC LIMIT 200;

3.229

SELECT SQL_NO_CACHE COUNT(1) FROM test.`UC_USER` t WHERE t.`CREATE_DATE` > ' 2016-07-01 10:26:36' ;

0.514

SELECT SQL_NO_CACHE COUNT(1) FROM test.`UC_USER_PK_VARCHAR_1` t WHERE t.`CREATE_DATE` > '2016-07-01 10:26:36' ;

1.092

PS: In the presence of cache, there is no small difference in execution efficiency between the two.

2.4 Write test, auto-increment ID is 4 times

##Primary key type##UPDATE test.`UC_USER` t SET t.`MOBILE_TGC`='T2' WHERE t.`CREATE_DATE` > ' 2016-05-03 10:26:36' AND t.`CREATE_DATE` <'2016-05-04 00:00:00' ;UUID0.105

SQL statement

Execution Time (seconds)

#Auto-increment ID

##1.419

##UPDATE test.`UC_USER_PK_VARCHAR_1` t SET t.`MOBILE_TGC`='T2' WHERE t.`CREATE_DATE` > ; '2016-05-03 10:26:36' AND t.`CREATE_DATE` <'2016-05-04 00:00:00' ;
5.639

Increase ID

##INSERT INTO test.`UC_USER`( ID, `USER_NAME`, `USER_PWD`, `BIRTHDAY`, `NAME`, `USER_ICON `, `SEX`, `NICKNAME`, `STAT`, `USER_MALL`, `LAST_LOGIN_DATE`, `LAST_LOGIN_IP`, `SRC_OPEN_USER_ID`, `EMAIL`, `MOBILE`, `IS_DEL`, `IS_EMAIL _CONFIRMED`, `IS_PHONE_CONFIRMED`, `CREATER`, `CREATE_DATE`, `UPDATE_DATE`, `PWD_INTENSITY`, `MOBILE_TGC`, `MAC`, `SOURCE`, `ACTIVATE`, `ACTIVATE_TYPE` ) SELECT NULL, `USER_NAME `,8 ), `USER_PWD`, `BIRTHDAY`, `NAME`, `USER_ICON`, `SEX`, `NICKNAME`, `STAT`, `USER_MALL`, `LAST_LOGIN_DATE`, `LAST_LOGIN_IP`, `SRC_OPEN_USER_ID`, `EMAIL`, CONCAT('110',TRIM(`MOBILE`)), `IS_DEL`, `IS_EMAIL_CONFIRMED`, `IS_PHONE_CONFIRMED`, `CREATER`, `CREATE_DATE`, `UPDATE_DATE`, `PWD_INTENSITY`, `MOBILE_TGC`, `MAC`, `SOURCE`, `ACTIVATE`, `ACTIVATE_TYPE` FROM `test`.`UC_USER_1` LIMIT 100;

UUID

INSERT INTO  test.`UC_USER_PK_VARCHAR_1`(     ID,   `USER_NAME`,   `USER_PWD`,   `BIRTHDAY`,   `NAME`,    `USER_ICON`,   `SEX`,   `NICKNAME`,   `STAT`,    `USER_MALL`,    `LAST_LOGIN_DATE`,   `LAST_LOGIN_IP`,   `SRC_OPEN_USER_ID`,   `EMAIL`,    `MOBILE`,   `IS_DEL`,   `IS_EMAIL_CONFIRMED`,   `IS_PHONE_CONFIRMED`,   `CREATER`,   `CREATE_DATE`,   `UPDATE_DATE`,   `PWD_INTENSITY`,   `MOBILE_TGC`,   `MAC`,    `SOURCE`,   `ACTIVATE`,   `ACTIVATE_TYPE` ) SELECT         UUID(),   CONCAT('110',`USER_NAME`,8),   `USER_PWD`,   `BIRTHDAY`,   `NAME`,    `USER_ICON`,   `SEX`,   `NICKNAME`,   `STAT`,    `USER_MALL`,    `LAST_LOGIN_DATE`,    `LAST_LOGIN_IP`,    `SRC_OPEN_USER_ID`,   `EMAIL`,  CONCAT('110',TRIM(`MOBILE`)),    `IS_DEL`,    `IS_EMAIL_CONFIRMED`,    `IS_PHONE_CONFIRMED`,    `CREATER`,   `CREATE_DATE`,   `UPDATE_DATE`,   `PWD_INTENSITY`,   `MOBILE_TGC`,   `MAC`,    `SOURCE`,   `ACTIVATE`,   `ACTIVATE_TYPE` FROM `test`.`UC_USER_1`  LIMIT 100;

0.424

 

 

 

 

3、总结

在500W记录表的测试下:

(1)      普通单条或者20条左右的记录检索,uuid为主键的相差不大几乎效率相同;

(2)      但是范围查询特别是上百成千条的记录查询,自增id的效率要大于uuid;

(3)      在范围查询做统计汇总的时候,自增id的效率要大于uuid;

(4)      在存储上面,自增id所占的存储空间是uuid的1/2;

 

 以上就是MySQL 使用自增ID主键和UUID 作为主键的优劣比较详细过程(500W单表)的内容,更多相关内容请关注PHP中文网(www.php.cn)!


Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

MySQL's Role: Databases in Web Applications MySQL's Role: Databases in Web Applications Apr 17, 2025 am 12:23 AM

The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

How to start mysql by docker How to start mysql by docker Apr 15, 2025 pm 12:09 PM

The process of starting MySQL in Docker consists of the following steps: Pull the MySQL image to create and start the container, set the root user password, and map the port verification connection Create the database and the user grants all permissions to the database

Laravel Introduction Example Laravel Introduction Example Apr 18, 2025 pm 12:45 PM

Laravel is a PHP framework for easy building of web applications. It provides a range of powerful features including: Installation: Install the Laravel CLI globally with Composer and create applications in the project directory. Routing: Define the relationship between the URL and the handler in routes/web.php. View: Create a view in resources/views to render the application's interface. Database Integration: Provides out-of-the-box integration with databases such as MySQL and uses migration to create and modify tables. Model and Controller: The model represents the database entity and the controller processes HTTP requests.

Solve database connection problem: a practical case of using minii/db library Solve database connection problem: a practical case of using minii/db library Apr 18, 2025 am 07:09 AM

I encountered a tricky problem when developing a small application: the need to quickly integrate a lightweight database operation library. After trying multiple libraries, I found that they either have too much functionality or are not very compatible. Eventually, I found minii/db, a simplified version based on Yii2 that solved my problem perfectly.

How to install mysql in centos7 How to install mysql in centos7 Apr 14, 2025 pm 08:30 PM

The key to installing MySQL elegantly is to add the official MySQL repository. The specific steps are as follows: Download the MySQL official GPG key to prevent phishing attacks. Add MySQL repository file: rpm -Uvh https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm Update yum repository cache: yum update installation MySQL: yum install mysql-server startup MySQL service: systemctl start mysqld set up booting

Laravel framework installation method Laravel framework installation method Apr 18, 2025 pm 12:54 PM

Article summary: This article provides detailed step-by-step instructions to guide readers on how to easily install the Laravel framework. Laravel is a powerful PHP framework that speeds up the development process of web applications. This tutorial covers the installation process from system requirements to configuring databases and setting up routing. By following these steps, readers can quickly and efficiently lay a solid foundation for their Laravel project.

MySQL and phpMyAdmin: Core Features and Functions MySQL and phpMyAdmin: Core Features and Functions Apr 22, 2025 am 12:12 AM

MySQL and phpMyAdmin are powerful database management tools. 1) MySQL is used to create databases and tables, and to execute DML and SQL queries. 2) phpMyAdmin provides an intuitive interface for database management, table structure management, data operations and user permission management.

Centos install mysql Centos install mysql Apr 14, 2025 pm 08:09 PM

Installing MySQL on CentOS involves the following steps: Adding the appropriate MySQL yum source. Execute the yum install mysql-server command to install the MySQL server. Use the mysql_secure_installation command to make security settings, such as setting the root user password. Customize the MySQL configuration file as needed. Tune MySQL parameters and optimize databases for performance.

See all articles