mirrors/gotosocial
1
0
Fork 0
mirror of https://github.com/superseriousbusiness/gotosocial.git synced 2026-01-06 02:43:17 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

[docs] rename assets to public to avoid conflicting with template

Browse source
This commit is contained in:
CDN18 2024-11-02 07:02:49 +08:00
commit e0b8d72641
No known key found for this signature in database
GPG key ID: 0C656827F9F80080
64 changed files with 45 additions and 45 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/getting_started/index.md
View file

@ -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 250MB 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.](../public/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).