Menu
  Log out
 

Satisfactory Server Performance Optimization Guide

Satisfactory Guide • Updated Jan 9, 2026

Satisfactory Server Performance Optimization Guide

Expert guide to maximizing performance on Satisfactory dedicated servers. Learn how to optimize tick rate, reduce memory usage, handle large factory saves, and eliminate lag for smooth multiplayer gameplay.

Note: Satisfactory 1.0 servers are CPU-bound, with performance heavily dependent on factory complexity and object count. Optimizing server settings can dramatically improve player experience.

Understanding Performance Bottlenecks

Primary Performance Factors

  • Object Count: Each building, conveyor, and item adds to CPU load
  • Network Replication: Data synchronization between server and clients
  • Save File Size: Large saves increase load times and memory usage
  • Tick Rate: Server updates per second (default 60, can be reduced)
  • Memory Usage: RAM consumption grows with factory size

Server Configuration Optimization

Critical ServerSettings.ini Tweaks

[/Script/Engine.GameSession] MaxPlayers=16 ServerName="Optimized Server" ServerPassword="" ServerDescription="Performance-optimized Satisfactory server" [/Script/FactoryGame.FGGameUI] mAutosaveInterval=900 ; Increase from 300 to reduce save spikes [/Script/Engine.NetworkSettings] NetServerMaxTickRate=45 ; Reduce from 60 for large factories MaxInternetClientRate=100000 MaxClientRate=100000 [/Script/FactoryGame.FGReplicationDetailActor] mCullDistance=50000 ; Increase to reduce actor replication mSignificanceRange=25000

Launch Parameters Optimization

# Recommended launch parameters for large factories -startserver -log -nosteamclient -unattended -ServerQueryPort=15777 -BeaconPort=15000 -Port=7777 # Memory management flags -USEALLAVAILABLECORES -malloc=system -nomansky -lowmemory # Disable unnecessary features -nohomedir -nosound -nullrhi

Memory Management Strategies

Reducing RAM Usage

Problem:

Satisfactory servers can consume 8-16GB+ RAM with large factories, causing crashes and slowdowns.

Solutions:

  1. Enable Texture Streaming: Set r.TextureStreaming=1 in Engine.ini
  2. Reduce View Distance: Lower r.ViewDistanceScale=0.7 in clients (not server)
  3. Clean Up Items: Remove abandoned items and debris with SCIM editor
  4. Memory Limit: Use -MaxMemoryUsage=8192 launch parameter (8GB limit)

Handling Large Save Files

Problem:

Save files over 100MB cause long save/load times and increased memory pressure.

Solutions:

  1. Increase Autosave Interval: Set mAutosaveInterval=1800 (30 minutes)
  2. Use Incremental Saves: Enable mUseIncrementalSaves=1 in Game.ini
  3. Compress Saves: Enable mCompressSaveGames=1 (adds CPU load)
  4. Manual Save Management: Keep only last 3-5 saves, archive older ones

Network Performance Optimization

Reducing Bandwidth and Lag

# Network optimization settings [/Script/Engine.NetworkSettings] NetServerMaxTickRate=30 ; For factories with 5000+ buildings NetClientMaxTickRate=30 MaxInternetClientRate=50000 ReplicationBandwidthLimit=5000000 # Actor replication culling [/Script/FactoryGame.FGReplicationDetailActor] mCullDistance=75000 mSignificanceRange=30000 bEnableCulling=1

Client-Side Optimizations

  • Reduce Graphics Settings: Lower shadow quality, post-processing, and effects
  • Disable Foliage: Set foliage density to minimum or use -NoFoliage
  • Update Drivers: Ensure latest GPU and network drivers
  • Wired Connection: Use Ethernet instead of Wi-Fi for stable latency

Factory Design for Performance

Efficient Building Practices

Best Practices:

  1. Minimize Conveyor Lengths: Shorter belts reduce update calculations
  2. Use Manifold Systems: Simpler than load balancers, less CPU intensive
  3. Limit Particle Effects: Reduce smoke, sparks, and visual effects
  4. Optimize Power Grid: Consolidate power plants and reduce wire complexity
  5. Avoid Excessive Lighting: Lights add to rendering and update costs

Problematic Constructions to Avoid

  • Massive Storage Arrays: Each storage container tracks individual items
  • Excessive Splitters/Mergers: Each adds to simulation complexity
  • Long Distance Belts: Prefer trains or drones for long-haul transport
  • Over-Clocked Machines: Higher clock speeds increase update frequency
  • Unnecessary Foundations: Large foundation areas increase collision checks

Monitoring and Diagnostics

Performance Monitoring Tools

# Windows Performance Monitor # Track: Process\Private Bytes, Processor\% Processor Time # Linux monitoring commands top -p $(pgrep FactoryServer) # CPU/RAM usage iftop -i eth0 # Network bandwidth iotop # Disk I/O # Satisfactory built-in stats Open console (~) and type: stat fps # Client FPS stat unit # Performance breakdown stat net # Network statistics

Identifying Performance Issues

SymptomLikely CauseSolution
Server tick rate drops below 30High object countReduce factory complexity, increase cull distance
Clients experience rubberbandingNetwork congestionLower NetServerMaxTickRate, optimize replication
Long save times (60+ seconds)Large save fileIncrease autosave interval, clean up with SCIM
Memory usage constantly increasesMemory leakRestart server daily, monitor with process explorer
Clients disconnect frequentlyPacket loss/timeoutCheck network stability, reduce bandwidth limits

Advanced Optimization Techniques

Engine.ini Tweaks

[/Script/Engine.RendererSettings] r.ShadowQuality=0 r.DistanceFieldShadowing=0 r.DistanceFieldAO=0 r.AmbientOcclusionLevels=0 r.DefaultFeature.AntiAliasing=1 r.Tonemapper.Quality=0 [/Script/Engine.StreamingSettings] r.Streaming.PoolSize=512 r.Streaming.UseFixedPoolSize=1 [/Script/Engine.GarbageCollectionSettings] gc.TimeBetweenPurgingPendingKillObjects=30 gc.MaxObjectsNotConsideredByGC=500000

Dedicated Server Hardware Recommendations

Small Factory (up to 1000 buildings):

  • CPU: 4+ cores @ 3.5GHz+
  • RAM: 8GB DDR4
  • Storage: SSD with 50GB free
  • Network: 100 Mbps upload

Large Factory (5000+ buildings):

  • CPU: 8+ cores @ 4.0GHz+
  • RAM: 16GB+ DDR4
  • Storage: NVMe SSD with 100GB+ free
  • Network: 500 Mbps+ upload

When to Upgrade Hardware

Consider upgrading your server when:

  • Tick rate consistently below 20 even after optimization
  • Memory usage exceeds 90% during normal operation
  • Save/load times exceed 5 minutes
  • More than 8 players experience simultaneous lag
  • Factory expansion plans exceed current capacity

Pro Tip: Regular server restarts (every 24 hours) can clear memory leaks and improve performance. Schedule restarts during low-activity periods.

Need optimized Satisfactory server hosting? Launch your Satisfactory server with Supercraft for premium hardware and automated performance tuning.

← Back to Satisfactory Guides
Top