diff options
| author |  tobi <31960611+tsmethurst@users.noreply.github.com> | 2024-09-23 18:53:33 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2024-09-23 18:53:33 +0200 |
| commit | e59d2384e88e8d04dc89838d0494304b3926f8d0 (patch) | |
| tree | dc5bf9d9116cb9899141e4b892438d8471ad4158 /docs/getting_started/index.md | |
| parent | [bugfix] add support for media with rotation contained in stream side data (#... (diff) | |
| download | gotosocial-e59d2384e88e8d04dc89838d0494304b3926f8d0.tar.xz | |
[chore/docs] More little tweaks (#3336)
* [chore/docs] More little tweaks
* width
* rule between theme figures (looks better on gh)
* weee
Diffstat (limited to 'docs/getting_started/index.md')
| -rw-r--r-- | docs/getting_started/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
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). |