diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/assets/getting-started-memory-graph.png | bin | 80749 -> 92039 bytes | |||
| -rw-r--r-- | docs/getting_started/index.md | 2 |
2 files changed, 1 insertions, 1 deletions
diff --git a/docs/assets/getting-started-memory-graph.png b/docs/assets/getting-started-memory-graph.png Binary files differindex 2a5bf1c17..79fceff4d 100644 --- a/docs/assets/getting-started-memory-graph.png +++ b/docs/assets/getting-started-memory-graph.png 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: - + 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). |
