3868 15.3.8 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · write-heavy workload is improved by 2.33% ~ 4.61%. 2.5.1.2 Test environment (AWS EC2） 2.5.1.2.1 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3 performance of v6.1.0 is improved by 2.85%. 2.5.2.2 Test environment (AWS EC2） 2.5.2.2.1 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3

3139 13.2.4 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · 59% ~ 4.85% in the write-heavy workload. 2.5.1.2 Test environment (AWS EC2） 2.5.1.2.1 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3 performance of v5.4.0 is improved by 3.16%. 2.5.2.2 Test environment (AWS EC2） 2.5.2.2.1 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3

26 15.3.8 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · com/cn/blogs/security/get-the-full-benefits- �→ of-imdsv2-and-disable-imdsv1-across-your-aws-infrastructure/">AWS EC2 �→ now uses IMDSv2 as the default metadata service. TiDB supports �→ backing up data from TiKV AWS IMDSv2 #16443 @pingyu When deploying TiDB on Amazon EC2, BR supports AWS Instance Metadata Service Version 2 (IMDSv2). You can configure your EC2 instance to allow BR to use the IAM role associated with

5232 15.3.8 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · com/cn/blogs/security/get-the-full-benefits- �→ of-imdsv2-and-disable-imdsv1-across-your-aws-infrastructure/">AWS EC2 �→ now uses IMDSv2 as the default metadata service. TiDB supports �→ backing up data from TiKV AWS IMDSv2 #16443 @pingyu When deploying TiDB on Amazon EC2, BR supports AWS Instance Metadata Service Version 2 (IMDSv2). You can configure your EC2 instance to allow BR to use the IAM role associated with

4880 15.3.8 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · single Coding Then write the code: package com.pingcap.txn; import com.zaxxer.hikari.HikariDataSource; import In the end, no books are left in inventory. 4.8.2.2.1 Write an optimistic transaction example Coding package com.pingcap.txn.optimistic; import com.zaxxer.hikari.HikariDataSource; import java.math

4807 15.3.8 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · single Coding Then write the code: package com.pingcap.txn; import com.zaxxer.hikari.HikariDataSource; import In the end, no books are left in inventory. 4.8.2.2.1 Write an optimistic transaction example Coding package com.pingcap.txn.optimistic; import com.zaxxer.hikari.HikariDataSource; import java.math

4400 15.3.8 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · #38980 @tangenta • Fix the issue that the tidb_decode_key function fails to correctly parse the en- coding of partitioned tables #39304 @Defined2014 • Fix the issue that gRPC error logs are not redirected single Coding Then write the code: package com.pingcap.txn; import com.zaxxer.hikari.HikariDataSource; import

2530 13.2.4 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · 3.0 is nearly the same as that of v5.2.2. 2.5.1.2 Test environment (AWS EC2） 2.5.1.2.1 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3 performance of v5.3.0 is reduced by 2.99%. 2.5.2.2 Test environment (AWS EC2) 2.5.2.3 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3 TPC-C

2347 13.2.4 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · Write and Update Index is slightly reduced. 2.5.1.2 Test environment (AWS EC2） 2.5.1.2.1 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3 performance of v5.1.0 is improved by 2.8%. 2.5.2.2 Test environment (AWS EC2) 2.5.2.3 Hardware configuration Service type EC2 type Instance count PD m5.xlarge 3 TiKV i3.4xlarge 3 TiDB c5.4xlarge 3 TPC-C

4997 15.3.8 Can the codec of TiDB guarantee that the UTF-8 string is memcom- parable? Is there any coding suggestion if our key needs to support UTF-8? · · · · · · · · · · · · · · · · · · · · · · · · · · single Coding Then write the code: package com.pingcap.txn; import com.zaxxer.hikari.HikariDataSource; import In the end, no books are left in inventory. 4.8.2.2.1 Write an optimistic transaction example Coding package com.pingcap.txn.optimistic; import com.zaxxer.hikari.HikariDataSource; import java.math