details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 1179 Figure 139: Dashboard Example 5 1180 Figure 140: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 431 Figure 52: Dashboard Example 5 432 Figure 53: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 1209 Figure 142: Dashboard Example 5 1210 Figure 143: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 1227 Figure 142: Dashboard Example 5 1228 Figure 143: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 1212 Figure 142: Dashboard Example 5 1213 Figure 143: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 1020 Figure 107: Dashboard Example 5 1021 Figure 108: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 467 Figure 52: Dashboard Example 5 468 Figure 53: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 447 Figure 52: Dashboard Example 5 448 Figure 53: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 1227 Figure 142: Dashboard Example 5 1228 Figure 143: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots

details about the primary key of the CLUSTERED type, refer to clustered index. The following two load diagrams shows the case where two tables without primary keys use SHARD_ROW_ID_BITS to scatter hotspots. 1255 Figure 142: Dashboard Example 5 1256 Figure 143: Dashboard Example 6 As shown in the load diagrams above, before setting SHARD_ROW_ID_BITS, load hotspots are concentrated on a single Region. After LAST_INSERT_ID() | +------------------+ | 1073741825 | +------------------+ The following two load diagrams shows the situations both before and after modifying AUTO_INCREMENT to AUTO_RANDOM to scatter hotspots