Versions: 8.0+

QuerySurge™ System Requirements

QuerySurge is an enterprise data testing solution that will typically be used to validate large data sets. Since you are testing either a Big Data store or Data Warehouse with potentially massive quantities of data, QuerySurge needs the right hardware to perform at speeds that will meet your team's needs.

Therefore, the more CPU, RAM and hard drive space you have, the better and faster QuerySurge performs.

For a trial setup, QuerySurge can be run on a desktop with modest resources (see tables below) but that will limit QuerySurge's performance and ability to scale.

For a POC setup, we recommend a CPU of at least 4 cores.  For RAM, we recommend a minimum of 16 GB.  For hard drive, we prefer solid state drives (SSD) over standard hard disk drives (HDD) as their performance can be upwards of 10x faster, but an HDD will work.

For a production setup, we recommend the CPU have a minimum of 8 cores. For RAM, we recommend a minimum of 16 GB. For hard drive, we prefer solid state drives (SSD) over standard hard disk drives (HDD) as their performance can be upwards of 10x faster, but an HDD will work. For a production environment, one size does not fit all. Please see the variables that affect performance below and speak with our team before selecting a production deployment.

Performance Variables

There are variables that may impact performance to take into consideration when planning your QuerySurge deployment architecture:

• The proximity of the source and target databases to QuerySurge, i.e., whether they are on the same network. The closer they are, the faster the data loads into QuerySurge for analysis.
• Native installs/bare metal servers perform better than VMs due to inherent latency issues caused by additional computational layers.
• Utilizing Solid State Drives (SSD) over traditional Hard Disk Drives (HDD) can significantly increase QuerySurge’s performance, depending on the speed and generation of the SSD and if network latency issues are removed (see above).
• Splitting application and database servers can increase performance and reliability as more memory and other resources can be allocated to each component, but it is dependent on how your tests are set up.
• The number of concurrent, active testers that will be running tests.
• The number of QueryPairs that will be executed and the sizes of datasets (actual size in bytes or # of rows and columns).
• The number of agents that will be running. Agents are multi-threaded, with the default setting at 3 concurrent queries per agent (a configurable parameter).
• For best performance QuerySurge components should be installed on machines which are dedicated for QuerySurge to prevent resource contention.

Disk Performance Considerations

• QuerySurge runtime processing is significantly Disk I/O dependent.

• As noted above, SSD is recommended over HDD. Guidelines include the following:

  Deployment	Recommended Disk Option
  Physical deployments	NVME SSDs are recommended over Standard SSDs
  Azure deployments	'Ultra SSD' recommended
  AWS deployments	'EBS Provisioned IOPS SSD Volumes' recommended

  If your environment is not listed here, please speak with your internal system administrators to determine an equivalent disk option.

• Maximized IOPS is strongly recommended. This value is system-dependent, so figures cannot be simply quoted; the upper range for the environment you have deployed should be targeted.
• Low latency is also a desirable disk characteristic.
• These comments generally apply similarly to both virtual and physical environments.
• Cloud-based infrastructures (Azure, AWS, Oracle, GCP, etc.) tend to limit Disk I/O by default; however this is usually a configurable option and should be maximized.

Browser Support

Browser

Chrome¹

Firefox¹

Edge^1,2

¹ Browser not supported on Linux desktop environments
² Legacy Edge ("EdgeHTML") not supported; Edge "IE Mode" is not supported.

Operating System Support

Operating System	Version
Windows Desktop	10 & 11
Windows Server	2016, 2019, 2022, 2025
Red Hat Enterprise Linux (RHEL)	81/91/101
Fedora Core	36-431

¹ Full Linux install required (minimal install not supported) 
 

Security Considerations

• QuerySurge should only be deployed behind an organization's firewall.
• In addition, we strongly recommend use of SSL/HTTPS for all deployments, whether trial deployments or production deployments.
• See this article for details on deploying QuerySurge with SSL/HTTPS.

Hardware Options

Below are minimum and recommended system requirements for the different setups - 1 for trial/evaluation installations, 1 for POC installations and 4 for production installations:
 

1. Trial/Evaluation Installation - Minimum Requirements
2. POC Installation - Recommended Requirements
3. Production Installation - Single Server Setup - Minimum Requirements 
4. Production Installation - Single Server Setup - Recommended Requirements 
5. Production Installation - Multi-Server Setup - Minimum Requirements 
6. Production Installation - Multi-Server Setup - Recommended Requirements
   
   Note: We recommend against installation on a laptop. Details are available in this article. It is also noteworthy that VDI is not supported.

1. Trial/Evaluation Installation - Minimum Deployment System Requirements

Single Server Setup (Trial/Evaluation)

Component	Installation	CPU	Memory	Disk I/O	Disk Space1
QuerySurge  (Application server, Database server, Agent)	All components installed on single desktop or server	2 cores	16 GB	Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.) Solid-state drives (SSD) recommended.	100 GB

¹ Disk space is critical for both data storage and data analysis engine

2. POC Installation - Recommended Deployment System Requirements
Note: One size does not fit all. Please feel free to speak or email with our team to size your optimal POC deployment environment.

Single Server Setup (POC)

Component	Installation	CPU	Memory	Disk I/O	Disk Space1
QuerySurge (Application server, Database server)	App & Database server installed on single desktop or server	4 cores minimum	16 GB minimum	Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.) Solid-state drives (SSD) recommended.	1 TB
QuerySurge Agent	Installed on separate  desktop(s) to alleviate resource contention	2 cores	8 GB	N/A	20 GB

¹ Disk space is critical for both data storage and data analysis engine

3. Production Installation - Minimum Deployment System Requirements

Single Server Setup

Component	Installation	CPU	Memory	Disk I/O	Disk Space2
QuerySurge (Application server, Database server)	App & Database server installed on single desktop or server	4 cores	16 GB	Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.) Solid-state drives (SSD) recommended.	minimum of 1 TB --------------- optional data storage drive3
QuerySurge Agent	Installed on separate  desktop(s) to alleviate resource contention	2 cores	8 GB	Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,1 in which case maximum IOPS is recommended.	20 GB

¹ Examples of setups where Agent machines are disk I/O sensitive include: a) Flat file data; b) XML file data; c) JSON file data; d) Parquet file data; 
² Disk space is critical for both data storage and data analysis engine
³ An optional data drive for persistent data storage, to separate persistent data storage from runtime disk usage; minimum 1 TB SSD or HDD (not required)

4. Production Installation - Recommended Deployment System Requirements

Note: One size does not fit all. Please feel free to speak or email with our team to size your optimal deployment environment.

Single Server Setup

Component	Installation	CPU	Memory	Disk I/O	Disk Space2
QuerySurge (Application server, Database server)	App & Database server installed on single desktop or server	8 cores minimum	32 GB minimum	Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.) Solid-state drives (SSD) recommended.	minimum of 1 TB --------------- optional data storage drive3
QuerySurge Agent	Installed on separate  desktop(s) to alleviate resource contention	2 cores	8 GB	Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,1 in which case maximum IOPS is recommended	20 GB

¹ Examples of setups where Agent machines are disk I/O sensitive include: a) Flat file data; b) XML file data; c) JSON file data; d) Parquet file data; 
² Disk space is critical for both data storage and data analysis engine
³ An optional data drive for persistent data storage, to separate persistent data storage from runtime disk usage; minimum 1 TB SSD or HDD (not required)

5. Production Installation - Minimum Deployment System Requirements

Multi-Server Setup

Component	Installation	CPU	Memory	Disk I/O	Disk Space2
QuerySurge Application server	Installed on separate  desktop or server to alleviate resource contention	4 cores	8 GB	The QuerySurge App server is generally not Disk I/O sensitive; note however that all export functions are disk dependent	500 GB
QuerySurge Database server	Installed on separate  desktop or server to alleviate resource contention	4 cores	16 GB	Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.) Solid-state drives (SSD) recommended.	minimum of 1 TB --------------- optional data storage drive3
QuerySurge Agent	Installed on separate  desktop(s) to alleviate resource contention	2 cores	8 GB	Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,1 in which case maximum IOPS is recommended	20 GB

¹ Examples of setups where Agent machines are disk I/O sensitive include: a) Flat file data; b) XML file data; c) JSON file data; d) Parquet file data; 
² Disk space is critical for both data storage and data analysis engine
³ An optional data drive for persistent data storage, to separate persistent data storage from runtime disk usage; minimum 1 TB SSD or HDD (not required)

6. Production Installation - Recommended Deployment System Requirements

Note: One size does not fit all. Please feel free to speak or email with our team to size your optimal deployment environment.

Multi-Server Setup
 

Component	Installation	CPU	Memory	Disk I/O	Disk Space2
QuerySurge Application server	Installed on separate  desktop or server to alleviate resource contention	4 cores minimum	16 GB minimum	The QuerySurge App server is generally not Disk I/O sensitive; note however that all export functions are disk dependent	100 GB minimum
QuerySurge Database server	Installed on separate  desktop or server to alleviate resource contention	8 cores minimum	32 GB minimum	Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.) Solid-state drives (SSD) recommended.	minimum of 1 TB --------------- optional data storage drive3
QuerySurge Agent	Installed on separate  desktop(s) to alleviate resource contention	2 cores	8 GB	Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,1 in which case maximum IOPS is recommended	20 GB

¹ Examples of setups where Agent machines are disk I/O sensitive include: a) Flat file data; b) XML file data; c) JSON file data; d) Parquet file data; 
² Disk space is critical for both data storage and data analysis engine
³ An optional data drive for persistent data storage, to separate persistent data storage from runtime disk usage; minimum 1 TB SSD or HDD (not required)

Please feel free to reach out to us for further questions on your QuerySurge setup.

*** These requirements are subject to change without notice. ***