transmogrifier: Fixing votes from Note to Answer

[akkoma] / docs / configuration / optimizing_beam.md

diff --git a/docs/configuration/optimizing_beam.md b/docs/configuration/optimizing_beam.md
index 1753620c900a1e75d6929815aa710940ccc1ff98..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
 
@@ -39,7 +41,7 @@ Disable the busy-waiting. This should generally only be done if you're on a plat
 
 ### 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:**