Server Performance & Optimization Guide

1. Java options: -Xmx8G -Xms8G (8GB RAM), 2. Paper/Spigot instead of Vanilla, 3. set render-distance to 8-10, 4. set Nether/End borders, 5. use chunk preloader, 6. view-distance limiting. Result: <5ms latency, 100+ players possible.

1. enable caching (browser cache, server cache with Redis), 2. compress images (WEBP), 3. minify CSS/JS, 4. use CDN (Cloudflare), 5. delete old database logs, 6. upgrade to SSD. Google PageSpeed >90 achievable.

1. set swappiness=10 (less swap use), 2. increase ulimits, 3. TCP tuning (TCP buffer), 4. SSD instead of HDD, 5. monitoring (Netdata), 6. move cron jobs to off-peak, 7. disable unused services.

1. enable TRIM (fstrim -v /), 2. noatime mount option, 3. set I/O scheduler to noop, 4. avoid swap on SSD. With SSD: 10-100x faster than HDD. For game servers: difference between lagging/no lag.

Test: top/htop – shows CPU%. RAM usage >80% = upgrade RAM. CPU >80% = upgrade CPU/cores. For game servers: usually RAM limit. For traffic-heavy sites: CPU more important. Measure with 'sar -u' over time.

Tools: Netdata (free, live), Prometheus + Grafana (advanced), Nagios (enterprise). Alerts: CPU >80%, RAM >80%, disk >90%, load >cores*2. Notifications: email, Slack, or webhook.

Minimal (<1% CPU). But: must configure well. Tips: stateful inspection instead of deep packet inspection, only needed ports, review rules regularly. For high traffic: consider ebtables/nftables (advanced).

Causes: 1. too many players (increase limit or reduce server count), 2. unoptimized plugins/mods, 3. malware/botnet (rare), 4. old hardware. Solution: upgrade CPU, set player limit, audit plugins.