qTest components (and prerequisites applications) communicate with each other via TCP and HTTP, so they can be installed on different systems, as long as they can connect via specific ports. Files that may need to be shared among services can be supported by a distributed file system like NFS or SMB. In QASymphony's production cloud deployment, each application has a dedicated server to ensure the best control, but that may not be necessary for an OnPremise deployment. For best practices, please see the examples provide in this article: Selecting your OS and Deployment Model 

Single Server

Below is the sizing guide for deploying all qTest products, prerequisite databases, and applications in ONE single server.

Single Server (All in One)
Total Users	100-200	200-400	400+
Concurrent Users	25-50	50-100	100+
# of Servers	1	1	see below
CPU, Memory	quad core, 16GB RAM	quad core, 32GB RAM
Total Disk Space	150GB HD	400 GB HD

 

Cluster and Load Balancing

Below is the sizing guide for deploying all qTest products in a cluster or load balancing model.

Cluster and Load Balancing
	Total Users	200-400	400-1000	1000-2000
	Concurrent Users	50-100	100-250	250-500
Manager, Parameters, Launch, Scenario/Pulse	# of Servers	1	1	2
	CPU, Memory	quad core, 8GB RAM	quad core, 16GB RAM	quad core, 16GB RAM
	Total Disk Space	50GB HD	100 GB HD	200 GB HD
Sessions	# of Servers	1	1	2
	CPU, Memory	quad core, 8GB RAM	quad core, 16GB RAM	quad core, 16GB RAM
	Total Disk Space	100 GB HD	200 GB HD	400 GB HD
Postgres DB, mongoDB, elasticsearch, redis, rabbitmq, poseidon, notification	# of Servers	1	1	1
	CPU, Memory	quad core, 16GB RAM	quad core, 32GB RAM	quad core, 64GB RAM
	Total Disk Space	150 GB HD	300 GB HD	600 GB HD
Insights	# of Servers	1	1	1
	CPU, Memory	quad core, 8GB RAM	quad core, 16GB RAM	quad core, 16GB RAM
	Total Disk Space	50 GB HD	100 GB HD	200 GB HD