From e59d2384e88e8d04dc89838d0494304b3926f8d0 Mon Sep 17 00:00:00 2001 From: tobi <31960611+tsmethurst@users.noreply.github.com> Date: Mon, 23 Sep 2024 18:53:33 +0200 Subject: [chore/docs] More little tweaks (#3336) * [chore/docs] More little tweaks * width * rule between theme figures (looks better on gh) * weee --- docs/getting_started/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/getting_started') diff --git a/docs/getting_started/index.md b/docs/getting_started/index.md index 95dcb8e22..cd79cb312 100644 --- a/docs/getting_started/index.md +++ b/docs/getting_started/index.md @@ -20,7 +20,7 @@ You can find more detail on system requirements below, but in short you should a For a small instance (1-20 active users), GoToSocial will likely hover consistently between 250MB and 350MB of RAM usage once the internal caches are hydrated: -![Grafana graph showing GoToSocial heap in use hovering around 300MB and spiking occasionally to 400MB-500MB.](../assets/getting-started-memory-graph.png) +![Grafana graph showing GoToSocial heap in use hovering around 250MB and spiking occasionally to 400MB-500MB.](../assets/getting-started-memory-graph.png) In the graph above you can see that RAM usage spikes during periods of load. This happens, for example, when when a status gets boosted by someone with many followers, or when the embedded `ffmpeg` binary is decoding or reencoding media files into thumbnails (especially larger video files). -- cgit v1.2.3