> For the complete documentation index, see [llms.txt](https://docs.uxwizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uxwizz.com/installation/requirements/server-specs-cpu-ram.md).

# Server specs (CPU, RAM)

First check the [software requirements](/installation/requirements.md). Server capacity depends on page complexity, visit duration, concurrent traffic, recording mode, and retained history. Monthly visit counts alone do not establish a reliable CPU, memory, or disk requirement.

For a new installation, use the [recommended Linux flow](/installation/setup-uxwizz-server/ubuntu-20.04.md) on a server you can resize. Measure representative traffic before committing to a long-term server size.

1. Check CPU, memory, free disk space, and database growth during normal traffic and peak periods.
2. Test the dashboard queries you use, including longer date ranges. A server that accepts tracking data can still be slow when querying a large history.
3. Measure [full recording](https://docs.uxwizz.com/installation/requirements/pages/-MlFhp-p5VUf_FwF-x-1#b.-full-page-recording) on your own pages. Dynamic content and long sessions can use substantially more storage and bandwidth than basic recording.
4. Set [retention tasks](/installation/optimization-tips/auto-delete-old-data-cron-jobs.md) and confirm they run. Keep space for updates, temporary files, and backups as well as the live database.
5. Increase the constrained resource, then measure again. For larger installations, consider a separate database server with your administrator.

Allocate memory across the database, PHP, web server, and operating system. Do not give every service the same assumed share of total RAM. See [optimization tips](/installation/optimization-tips.md) for checks before tuning.

Disable collection features you do not need. For example, retaining session statistics longer than detailed recordings can reduce storage while preserving traffic history.

Keep backups outside the public web directory and test restoration. A successful backup job alone does not prove recoverability; see the [migration guide](/guides/migrating-to-a-new-server.md).

If you need help sizing a server, contact [support](/guides/support.md) with your traffic range, recording mode, retention period, and measured database growth. Do not send credentials or visitor records.