# How many resources is too many?

> What resource count really costs a FiveM server: script vs stream-only packs, startup time, pool size errors and how to audit a bloated server.

Source: https://fam-tools.com/guides/fivem-too-many-resources · FAM Tools · published 2026-09-11 · updated 2026-09-11 · about 10 min

**Short answer.** There is no single safe resource count. Script resources cost CPU (check resmon), stream-only resources cost download size and memory, and very large asset counts can exceed game pools such as `TxdStore`. Pools can be raised within limits with `increase_pool_size` in server.cfg (checked against Cfx.re’s allowed maximums); inspect them in F8 → Tools → Streaming → Pool Monitor. Audit regularly: remove unused and duplicate resources, and fix the heavy ones before worrying about the count.

## Key points

- Count is not the problem; cost per resource is.
- Scripts cost CPU; streamed assets cost memory and download.
- Pool errors → `increase_pool_size`, within Cfx.re limits.
- Pool Monitor: F8 → Tools → Streaming → Pool Monitor.
- Remove duplicates and unused packs first.

Servers with 300 or 400 resources are common, and owners often blame the number itself when things go wrong. The count matters less than what each resource does: a stream-only car costs memory and download size, a script that loops every frame costs CPU for every player, and too many assets of one type can exhaust a game pool.

## What each kind of resource costs

| Resource type | Main cost | Check with |
| --- | --- | --- |
| Client scripts | CPU every frame or tick | `resmon 1` |
| Server scripts | Server thread time | Profiler, hitch warnings |
| Stream-only (cars, MLOs, clothes) | Download size, streaming memory | Oversized warnings, pack sizes |
| NUI resources | Rendering and memory | FPS with UI open/closed |

## Pool size errors

GTA V allocates fixed-size pools for things like texture dictionaries and objects. Servers with huge asset counts can hit them, which shows up as crashes or assets that refuse to load. FiveM lets servers raise selected pools at startup:

*server.cfg*

```cfg
increase_pool_size "TxdStore" 6000
increase_pool_size "CMoveObject" 15
```

*A selection from Cfx.re’s server command documentation; the server rejects increases above the allowed limit.*

| Pool | FiveM maximum increase |
| --- | --- |
| TxdStore | 26000 |
| FragmentStore | 14000 |
| Building | 20000 |
| Object | 2000 |
| CMoveObject | 600 |

Pool changes can only be set at startup, and players whose game used different pool sizes restart once when joining. Inspect current usage in F8 → Tools → Streaming → Pool Monitor before raising anything.

## Auditing a bloated server

1. List every started resource and what it is for; remove what nobody can explain.
2. Find duplicates: two resources streaming the same file names, two HUDs, two garages.
3. Check resmon on a busy evening and fix the top offenders.
4. Review streamed packs by size — see [texture optimisation](https://fam-tools.com/guides/fivem-texture-optimization).
5. Keep categories in bracket folders (`[cars]`, `[maps]`) so `ensure` order stays clear.

## Slow startups

More resources mean a longer start. On Windows, antivirus scanning is a frequent extra cause — Cfx.re recommends excluding the server folder from Microsoft Defender. Details: [Windows server setup](https://fam-tools.com/guides/fivem-windows-server-setup).

## Questions

### How many resources can a FiveM server have?

There is no fixed number. What matters is each resource’s CPU, memory and asset cost, and whether game pools run out.

### How do I fix pool size errors?

Raise the affected pool with `increase_pool_size "PoolName" amount` in server.cfg, within Cfx.re’s allowed limits.

### Do stream-only resources affect performance?

They cost download size and streaming memory rather than CPU; oversized ones cause texture loss.

### Where can I see pool usage?

In game: F8 → Tools → Streaming → Pool Monitor.

## Related

- https://fam-tools.com/guides/fivem-server-performance
- https://fam-tools.com/guides/fivem-texture-optimization
- https://fam-tools.com/guides/fivem-oversized-assets-warning
- https://fam-tools.com/guides/fivem-server-thread-hitch-warning