From 7f18af844a09ee2ddcb8bb99f7622e37ec320f5d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ramiro=20Nu=C3=B1ez=20Dosio?= Date: Thu, 8 Sep 2022 11:38:58 +0100 Subject: [PATCH] Fixed image. --- apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx b/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx index a7114f754c0..cf91c7cc6af 100644 --- a/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx +++ b/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx @@ -351,7 +351,7 @@ SELECT COUNT(idkit_ksuid_generate()) FROM generate_series(1, 1000000); Running all of the ID generation mechanisms on a *single core* of my machine (which happens to be an [Oryx Pro](https://system76.com/laptops/oryx)), the lowest of 5 runs for each ID looks like this: -!(Generation speed test)[/images/blog/primary-keys/generation-speed-chart.jpg] +![Generation speed test](/images/blog/primary-keys/generation-speed-chart.jpg) To be fair, **generation speed shouldn’t be a deal breaker** as it’s unlikely to be the bottle neck for most applications. That said, it is nice to have some data on where each ID generation mechanism lands.