6 ms·
What database were you using? For example with SQL server, by default it clusters data on disk by primary key. Random (non-sequential) PKs like uuidv4 require r
by cipehr 11mo ago
What database were you using? For example with SQL server, by default it clusters data on disk by primary key. Random (non-sequential) PKs like uuidv4 require random cluster shuffling to insert a row “in the middle” of a cluster, increasing io load and causing performance issues.
Postgres on the other hand doesn’t do clustered indexing on the PK… if I recall correctly.
- rvitorper 11mo agoPostgres. It was also a single instance, which made it significantly easier. But nice to know that this is an issue on SQL Server
- masklinn 11mo agoPostgres is not immune to uuid issues, just less sensitive, uuidv4 still does not play well with btree indexes, bloating them and impacting their performance.
- ahoka 11mo agoThen cluster it differently? The whole problem uuidv7 in databases solves is a non-issue in most cases.