Server Process Settings
Learning Focus
By the end of this lesson you will understand how OpenLiteSpeed process settings work, what to tune, and how to verify your configuration.
What Process Settings Control
Server process settings shape how OpenLiteSpeed starts workers, which user it runs as, and how it behaves during restarts or high load.
Key Settings
| Setting | Default | What It Does |
|---|---|---|
| User | nobody | Linux user the server runs as |
| Group | nogroup | Linux group the server runs as |
| Priority | 0 | Process niceness (lower = higher priority) |
| Max Workers | Auto | Number of worker processes |
| CPU Affinity | 0 | Bind workers to specific CPU cores |
Checking Current Settings
# Check which user OpenLiteSpeed runs as
ps aux | grep lshttpd | head -5
# Check process count
ps aux | grep lshttpd | grep -v grep | wc -l
# Check resource usage
top -p $(pgrep -d',' lshttpd)
Configuring in WebAdmin
- Navigate to Server Configuration → General
- Adjust User, Group, and Priority as needed
- Navigate to Server Configuration → Tuning
- Adjust worker-related settings
- Save and Graceful Restart
info
In most cases, the defaults work well. Only tune process settings after measuring actual performance under your workload.
Key Takeaways
- Process settings shape the server's stability envelope under real traffic.
- The server user (typically
nobody) affects file permissions throughout the stack. - Tune conservatively and measure before changing defaults.
What's Next
- Continue to Connection Settings for timeout and concurrency tuning.