Before You Install the Experience Service > System Requirements > Hardware Sizing
  
Hardware Sizing
Hardware requirements depend on whether the Experience Service is running on the same hardware as the required ThingWorx server, or on separate hardware. The following are minimum recommendations for production.
* 
Actual sizing depends on the application and usage scenarios.
Experience Service Installed Separately from ThingWorx Server (Basic authentication only)
The following hardware sizing guidelines assume that while using basic authentication, the Experience Service is installed on different hardware than the required ThingWorx server.
* 
If in the future, you choose to move to SSO authentication, you will need to reconfigure so that both ThingWorx and the Experience Service are on the same server.
Aspect
Value
Description
Memory
4 GB
CPU(s)
2 Cores
Virtualized environments may use unique terminology for specifying how many CPUs/Cores are being provided. This must be taken into account when determining if the environment meets the minimum requirements.
Experience publishing places the heaviest load on the CPU and the size of the experience being published determines how much of the CPU a publishing request uses. In the absence of publishing, a two-core system can accommodate the typical activity of several thousand non-publishing users assuming a sustained request arrival rate of 10 requests per second.
Disk Type
*
Server-class hardware is recommended.
Disk Space
1 GB
Disk space size accommodates the Experience Service installation including, Node.js and required node modules. It also accommodates the creation of the initial tables in a SQLite database (if SQLite is being used).
• This does NOT include the space required for the OS, required ThingWorx server, or PostgreSQL database (if PostgreSQL is being used).
• Additional space is required to store published experience content. The total additional disk space required depends on the size and complexity of published Experiences. The size of each experience is approximately 2 MB, not including the 3D graphics data included in the experience. The size of the 3D graphics data can vary greatly depending on complexity and quality.
• Additional space is also required for log files. Log files can grow very large depending on use. It is recommended that you use syslog and log rolling.
Disk Speed
*
No specific recommendation currently. Under normal conditions, disk I/O is not an issue unless multiple projects are being published concurrently.
Experience Service Co-Installed with ThingWorx Server
If the Experience Service is installed on the same hardware as the required ThingWorx server, then the minimum hardware requirement depends on the number of active Experience Service users. The following table provides additional hardware resources required above what is recommended for the co-installed ThingWorx server. For more information on the minimum hardware size requirements for the ThingWorx server, see the ThingWorx documentation.
# of Users
Recommendation
< 500
No additional hardware resources are required. This assumes a sustained request arrival rate of no more than 1 request per second.
500-1000
1 additional CPU core is recommended. This assumes a sustained request arrival rate of no more than 5 requests per second.
> 1000
For this number of active users, it is recommended that the Experience Service be installed separately from the ThingWorx server. This assumes a sustained request arrival rate of 10 requests per second or greater.