Optimised UUIDs in mysql
Read OriginalThis 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.
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
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
Container queries are rad AF!
Chris Ferdinandi
•
2 votes
3
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
4
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
5
Wagon’s algorithm in Python
John D. Cook
•
1 votes
6
An example conversation with Claude Code
Dumm Zeuch
•
1 votes