From 1c5bdd99535bac92fdba93a53c082f34950023c9 Mon Sep 17 00:00:00 2001 From: BraydonKains Date: Sat, 7 Feb 2026 09:57:16 -0500 Subject: [PATCH] fix image link --- content/blog/go-binary-size-mem-usage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/go-binary-size-mem-usage.md b/content/blog/go-binary-size-mem-usage.md index 41faea9..3d4bd79 100644 --- a/content/blog/go-binary-size-mem-usage.md +++ b/content/blog/go-binary-size-mem-usage.md @@ -14,7 +14,7 @@ I ran the two collectors at the same time on my machine, using [this config](htt Once these were both running, I checked `htop`, pressing `F4` with the filter `otelcol` so we can look at both processes. I got the following result: -![htop screenshot showing otelcol-contrib using 4.4% of system memory, whereas otelcol is only using 1.9%](/htop_otelcol.jpg) +![htop screenshot showing otelcol-contrib using 4.4% of system memory, whereas otelcol is only using 1.9%](/htop_otelcol.png) `otelcol-contrib` is using 4.4% of system memory, with `otelcol` only using 1.9%, basically half. The `RES` and `SHR` values for each of these processes reflects that difference directly. Why is it that two processes largely built from the same code, running the same codepaths since they are on the same config, have such a large amount of difference in memory usage?