| Clan\/competitive, 300+ players<\/td> | 32+<\/td> | 96-128 GB<\/td> | NVMe 4 TB (RAID 10)<\/td> | 6000 + custom<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nWhy 64 GB Is the Real Entry Point for Big Wipes<\/h3>\n\n\n\nRust servers leak memory across long uptimes \u2014 not a bug so much as accumulation of entity references and the Unity garbage collector’s reluctance to compact under sustained load. A server that starts a wipe at 18 GB RSS can reach 40 GB by day 20. On a 32 GB box, that means a scheduled restart every 12-24 hours. On 64 GB, you can run 3-5 days between restarts, which is far friendlier to a populated server.<\/p>\n\n\n\n CPU: Clocks Beat Cores (With a Caveat)<\/h2>\n\n\n\nRust’s server tick and entity simulation thread benefits from high single-thread clock speed, but unlike Minecraft it uses significant parallelism for physics, networking, and anti-cheat. The practical sweet spot for a 200-player server is 16 cores at 4.5+ GHz base. Beyond 24 cores, returns diminish unless you are running multiple instances.<\/p>\n\n\n\n Wipe-day generation is the exception: it will saturate all available cores for several minutes. If your operation accepts player joins immediately on wipe, 16+ cores materially reduce the “map still generating” window.<\/p>\n\n\n\n Storage and the Wipe-Day I\/O Burst<\/h2>\n\n\n\nRust saves the entire world to disk on a schedule controlled by server.saveinterval<\/code> (default 600 seconds). A 200-player server with a 6000 map produces save files of 1-5 GB. Every 10 minutes, the server writes that in one operation, then compresses it.<\/p>\n\n\n\n- Use NVMe, not SATA. Save operations that take 400 ms on NVMe take 3+ seconds on SATA \u2014 and the server stutters during the write.<\/li>
- Keep
server.saveinterval<\/code> at 300-600 for populated servers; do not extend it to reduce I\/O, as longer intervals mean bigger writes and worse worst-case stalls.<\/li>- Store backups on a separate volume or remote object storage. Never on the live server’s boot disk.<\/li><\/ul>\n\n\n\n
Network Sizing<\/h2>\n\n\n\nRust traffic is bursty and entity-driven. A player standing in a base sees minimal traffic; a raid with 40 players and thousands of entities in view can push 200 Kbps per player. Plan on 1 Mbps of commit per 15-20 concurrent players at peak, with a 1 Gbps port. Monthly traffic for a 200-player monthly-wipe server typically lands between 8 and 20 TB.<\/p>\n\n\n\n DDoS exposure matters more for Rust than most games because public server lists attract volumetric attacks. Dedicated IPs with always-on filtering are worth the cost over the “on-demand” model that requires you to notice the attack first.<\/p>\n\n\n\n
|