Merge branch 'builder-note' into 'develop'

[akkoma] / docs / configuration / optimizing_beam.md

diff --git a/docs/configuration/optimizing_beam.md b/docs/configuration/optimizing_beam.md
index 545392f8f6e70af9de83d1bbe5a79a017bb35b0c..e336bd36cd8b68f75ab763712b9b41754a1d67fc 100644 (file)
--- a/docs/configuration/optimizing_beam.md
+++ b/docs/configuration/optimizing_beam.md
@@ -6,11 +6,13 @@ This strategy is very successful in making a performant and responsive applicati
 
 More adventurous admins can be creative with CPU affinity (e.g., *taskset* for Linux and *cpuset* on FreeBSD) to pin processes to specific CPUs and eliminate much of this contention. The most important advice is to run as few processes as possible on your server to achieve the best performance. Even idle background processes can occasionally create [software interrupts](https://en.wikipedia.org/wiki/Interrupt) and take attention away from the executing process creating latency spikes and invalidation of the CPU caches as they must be cleared when switching between processes for security.
 
+Please only change these settings if you are experiencing issues or really know what you are doing. In general, there's no need to change these settings.
+
 ## VPS Provider Recommendations
 
 ### Good
 
-* ????
+* Hetzner Cloud
 
 ### Bad
 
@@ -27,7 +29,7 @@ Check your OS documentation to adopt a similar strategy on other platforms.
 
 ### Virtual Machine and/or few CPU cores
 
-Disable the busy-waiting
+Disable the busy-waiting. This should generally only be done if you're on a platform that does burst scheduling, like AWS.
 
 **vm.args:**
 
@@ -39,7 +41,7 @@ Disable the busy-waiting
 
 ### Dedicated Hardware
 
-Enable more busy waiting, increase the internal maximum limit of BEAM processes and ports
+Enable more busy waiting, increase the internal maximum limit of BEAM processes and ports. You can use this if you run on dedicated hardware, but it is not necessary.
 
 **vm.args:**