News for hackers. Stuff that matters.

A comment on UUIDs are popular, but bad for performance (2019). Parent comment

Re:UUIDs are popular, but bad for performance (2019) by dllthomas on Saturday January 08, 2022 @12:31PM (#29853890)
> Or reverse the time fields during indexing (slower, but still not as slow as an unnecessary disk read!).

When you're IO bound, I'm not sure it actually is slower in practice.

[ Parent | on HN ]
Re:UUIDs are popular, but bad for performance (2019) by colanderman on Saturday January 08, 2022 @02:15PM (#29855082)
Depending on caching strategy, using random UUIDs also decreases the maximum working set size before you become I/O bound by a huge factor. Postgres e.g. relies heavily on the O/S block cache and is subject to this.
[ Parent | on HN ]
Re:UUIDs are popular, but bad for performance (2019) by dllthomas on Saturday January 08, 2022 @07:56PM (#29858553)
> using random UUIDs

I wasn't discussing using random UUIDs.

[ Parent | on HN ]