HogWarp Server Performance and Resource Requirements
Understand HogWarp's RAM, CPU, and storage requirements and how to tune your server for best performance.
HogWarp Server Performance and Resource Requirements
HogWarp runs as a Windows binary under Wine on Linux, which has some specific implications for resource usage. This article covers the minimum and recommended specs, how player count affects performance, and practical tuning tips.
Minimum and Recommended Resources
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 250 MB | 1 GB or more |
| Storage | 1.5 GB | 2 GB+ (with backups) |
| CPU | 1 vCPU | 2+ vCPUs |
| Network | 10 Mbps | 100 Mbps |
The 250 MB minimum is tight — the server can run, but you may experience instability or crashes under any real player load. Allocate at least 1 GB RAM for a stable public server.
RAM Usage by Player Count
HogWarp's memory usage scales with connected players. As a rough guide:
| Players | Estimated RAM |
|---|---|
| 0–4 | ~300–400 MB |
| 5–8 | ~500–700 MB |
| 9–16 | ~800 MB–1.2 GB |
| 16+ | 1.5 GB+ |
These are estimates — actual usage depends on in-game activity. Plan conservatively and monitor usage.
Wine Overhead
Because the server runs under Wine, there is additional overhead compared to a native Linux binary:
- Wine itself consumes roughly 50–100 MB of RAM on top of the server process
- CPU overhead from Wine's Windows API translation is generally low for this workload but can spike during heavy I/O
- The
.NET 7runtime inside Wine adds to the memory baseline
This is normal and expected. DustBowl.Games accounts for this overhead in its HogWarp server allocations.
Storage Breakdown
| Component | Size |
|---|---|
| HogWarpServer binary + DLLs | ~200–300 MB |
| Wine prefix (with dotnet7) | ~1 GB |
| Server Data/ directory | Grows over time with player data |
The Wine prefix with dotnet7 is the largest single component. Keep at least 500 MB of free space beyond the initial install to accommodate the Data/ directory growing over time.
Monitoring Server Performance
Check memory and CPU usage of the running Wine process:
# Find the process
ps aux | grep HogWarpServer
# Detailed memory stats
cat /proc/$(pgrep -f HogWarpServer)/status | grep -E "VmRSS|VmSwap"
To monitor in real time:
top -p $(pgrep -f HogWarpServer)
Log Files and Disk Usage
Server logs go to stdout. If you redirect them to a file, they can grow large over time:
wine HogWarpServer.exe > server.log 2>&1 &
Rotate or truncate server.log periodically to prevent it from filling your storage:
# Truncate log (server keeps running)
> /home/container/server.log
Swap Space
If your server has limited RAM, swap space can prevent out-of-memory crashes but will cause significant performance degradation. A swap file is a last resort — upgrade your RAM allocation instead if the server is consistently hitting its limit.
DustBowl.Games Hosting Plans
DustBowl.Games recommends at minimum a plan with 1 GB RAM for HogWarp. If you plan to run near your Patreon tier's maximum player count, choose a plan with 2 GB or more. Contact support if you are unsure which plan fits your needs.