# FiveM Server Performance – Fix Lag, FPS Drops & Tickrate

FiveM server lagging? FPS drops, bad tick rate, OneSync & script optimization – step-by-step performance troubleshooting.

**Quick answer:** Fix FiveM lag by checking resmon for heavy scripts, optimizing OneSync, upgrading RAM/CPU and tuning server.cfg settings.

This guide shows you how to improve your FiveM server's performance and reduce server load. The tips apply to Linux and Windows as well as ESX, QBCore and most other frameworks.

## Optimize server hardware

    - **CPU:** FiveM benefits greatly from high single-core performance. A modern processor with 4+ cores and high clock speed is ideal
- **RAM:** 8 GB minimum, 16 GB for servers with many resources and players
- **Storage:** NVMe SSD is mandatory – HDD causes massive lags and long loading times

## Keep server software up to date

    - Regularly download the latest recommended FiveM server build
- Update txAdmin via the dashboard
- Keep all resources and scripts up to date

## Optimize server.cfg

These settings in server.cfg have a major impact on performance:

`sv_maxclients 32
sv_enforcegamebuild 0
onesync_enabled 1
onesync_population true
sv_scriptHookAllowed 0`

    - **sv_maxclients:** No more slots than needed – each reserved slot consumes resources
- **onesync_enabled:** Enables OneSync for better performance with many players
- **sv_scriptHookAllowed:** Keep disabled, reduces abuse and saves resources

## Clean up resources

    - Only start resources that are actually needed
- Leave unused resources in the folder but comment them out from `ensure`
- Test new scripts individually – poorly programmed scripts are often the main cause of lags
- Delete old and outdated resources

## Optimize database

    - Regularly delete old entries from the database (logs, old vehicles, inactive accounts)
- Set database indexes for frequently queried tables
- Use separate database for development and live server

## Streaming optimization

    - Optimize large MLOs and maps – remove unused areas
- Limit streaming distance for objects and vehicles sensibly
- Compress textures and models
- Avoid too many custom vehicles – every loaded vehicle costs performance

## txAdmin performance check

    - Check dashboard regularly – keep an eye on CPU and RAM usage
- Search the console for repeated error messages
- Schedule server restarts (every 12-24 hours)

## Configure automatic restart

A daily restart prevents memory leaks and keeps the server stable:

### Linux (Cronjob)

`crontab -e`
`0 6 * * * /home/fivem/fxserver/server/restart.sh`

### Windows (Task Scheduler)

Create a scheduled task that restarts the server daily.

## Common performance killers

    - **Too many vehicles:** Every vehicle model loads textures and models
- **Poorly programmed scripts:** Avoid infinite loops and inefficient queries
- **Too many players on one core:** FiveM mainly uses one thread
- **Many MLOs simultaneously:** Intelligently load and unload building interiors
- **Unnecessary blips and markers:** Each map blip costs minimal but accumulating resources

## Quick checklist

    - Use the latest FiveM build
- Enable OneSync
- Stop unused resources
- Clean up database
- Limit streaming distances
- Set up daily restart
- Monitor CPU and RAM usage