Server specs (CPU, RAM)

A lot of effort has been put into making the tracking and dashboard as fast as possible. UXWizz should run well on most servers, but depending on the amount of traffic you get and the total database size you should consider the following suggestions for your server configuration:

The full session recording system uses a lot more resources than the default one. Depending on the content on the site being tracked, you might need more resources.

Minimum recommended server specifications:

  • <10k monthly visits

    • Any cheap VPS or shared hosting should work

    • 1 GB RAM

    • 1 vCPU

    • 10GB disk

    • You should consider upgrading your server if you store more than 500k total sessions

  • <50k monthly visits

    • 2 GB RAM

    • 2 vCPU

    • 25GB disk

    • You should consider upgrading your server if you store more than 1M total sessions

  • <200k monthly visits

    • 8GB RAM

    • 4 vCPU

    • 50GB disk

    • You should consider upgrading your server if you store more than 5M total sessions

  • <1M monthly visits

    • 32GB RAM

    • 8 vCPU

    • 320GB disk

    • You should consider upgrading your server if you store more than 10M total sessions

  • 1M+ monthly visits

    • Powerful dedicated server

    • Preferably separate the MySQL database on a different server instance

Other recommendations:

  • Make sure your server resources are properly allocated.

    Check the MySQL, Apache and PHP configurations to make sure they have access to utilize all the resources provided by the server. See the optimization tips for some configuration suggestions.

  • Regularly back-up the database. I recommend an external backup service like SimpleBackups.io because it's easy to set-up and you get notified if the backup fails. They also have a free plan for a single project. Otherwise you could regularly save the output of mysqldump.

  • If you don't use all the features, disable them. UXWizz allows you to granularly set what data is being tracked (click heatmaps, movement heatmaps, recordings). If you do not use heatmaps for example, you can disable them in order to reduce data transfer and storage. In order, the most resource-intensive features are:

    • Session Recordings (when used, the default one is recommended for best performance).

    • Movement Heatmaps

    • Click Heatmaps

  • Suggestion to reduce total storage size over the years: keep all quantitative data (stats, page visits, events) but regularly delete old qualitative data (heatmaps, session recordings).

If you can't decide what server configuration or hosting provider to use, you can contact support for help and suggestions.

Last updated