workaround for uuid column type #555
Unanswered
yaozhiwang
asked this question in
Q&A
Replies: 1 comment 5 replies
-
Hi @yaozhiwang, I'm curious if the index has become too large to fit into memory on your database. To figure this out, you could run:
To find the size of the index being used for that query. If it is too large, then upgrading to a larger database would help performance. There are options for storing UUIDs in mysql more efficiently. But given that you don't own the application, I don't believe that's a feasible option for you. Generally we recommend people use auto incrementing big ints for IDs as they are the most space efficient and ordered. More info here on using UUIDs with MySQL. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
I am using umami for web analytics, with the database backed by PlanetScale. I am currently encountering a server performance issue, as discussed here. Some individuals have resolved this by altering the id column to a UUID column. Unfortunately, MySQL does not support the UUID type. I am wondering if there are any workarounds for this issue.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions