Brent • 11/29/2017

Optimised UUIDs in mysql

Read Original

This technical article details the performance drawbacks of storing UUIDs as CHAR(36) in MySQL and proposes a two-part optimization: storing UUIDs as binary data in a BINARY field for better indexing, and bit-shifting time-based bits (in UUIDv1) to create ordered data for superior index performance on large datasets. It includes benchmark comparisons and discusses when to use UUIDs.

0 comments
#indexing #mysql #uuid
Optimised UUIDs in mysql

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React vs Browser APIs (Mental Model)
Jivbcoop • 4 votes
2
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 3 votes
3
Building Type-Safe Compound Components
TkDodo Dominik Dorfmeister • 2 votes
4
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
5
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes
6
Better react-hook-form Smart Form Components
Maarten Hus • 1 votes
7
Building a Complete FIRE Calculator App with GitHub Copilot in One Chat Session
James Montemagno • 1 votes