common-pitfalls-and-best-practices too

common-pitfalls-and-best-practices.md

@@ -18,4 +18,6 @@ Shared hosts are usually the cheapest option, and that's for a valid reason. The
 Datapacks that run commands are extremely laggy. It may not be much with a few players on, but that doesn't scale well with the playercount and will lag your server pretty quickly as you gain players. Datapacks that modify biomes, loot tables, etc are fine. You're better off looking for a plugin alternative.
 
 ## Choosing hardware
-Don't just go off how much RAM you need. That's basically a non-issue, as you can run 100+ players on less than 16GB RAM with a lot of room to spare (unless you're using questionable plugins that cache unnecessary things). CPU is probably most important piece of the puzzle. You want something that [ranks good on single core performance](https://www.cpubenchmark.net/singleThread.html), as server's main thread runs on just one thread. It's important to note that this does not mean the entirety of the server uses only one thread. Multiple threads are utilised for quite some time now in systems like async chunk loading on paper. You should absolutely avoid HDD drives. Their speeds are simply way too slow to to justify running a server on them, and minecraft is heavy on I/O operations, especially with high viewdistances and higher playercounts.
+Don't just go off of how much RAM you need. You should instead focus on what kind of CPU you should use, since the CPU is the most important part of the server. You want something that [ranks good on single core performance](https://www.cpubenchmark.net/singleThread.html), as a server mainly runs on one thread. Multiple threads are utilised for quite some time now in systems like async chunk loading on paper, however.
+
+You should absolutely avoid HDD drives. Their speeds are simply way too slow to justify running a server on them since minecraft is heavy on I/O operations (especially with high view distances and higher player counts).