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 production setup, we recommend the CPU have a minimum of 8 cores, which Intel’s Xeon chip and other manufacturers’ chips provide in two quad (4) core processors. 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).
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 - 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 | Version |
Chrome1 | 16.0+ |
Firefox1 | 15.0+ |
Edge1,2 | 79+ |
1 Browser not supported on Linux desktop environments
2 Legacy Edge ("EdgeHTML") not supported; Edge "IE Mode" is not supported.
Hardware Options
Below are minimum and recommended system requirements for the different setups - 2 for trial installations and 4 for production installations:
- Trial/POC Installation - Minimum Requirements
- Trial/POC Installation - Recommended Requirements
- Production Installation - Single Server Setup - Minimum Requirements
- Production Installation - Single Server Setup - Recommended Requirements
- Production Installation - Multi-Server Setup - Minimum Requirements
- Production Installation - Multi-Server Setup - Recommended Requirements
1. Trial/POC Installation - Minimum Deployment System Requirements
Single Server Setup (Trial/POC)
Component1 | Installation | Supported Operating Systems (64-bit)2,a |
CPU | Memory | Disk I/O | Disk Space4 |
QuerySurge (Application server, Database server, Agent) |
All components installed on single desktop or server | Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/83; Fedora core 20-363 |
2 cores | 8 GB | Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.)5 |
100 GB |
a RHEL 6 - EOL as of 11/30/20 and is no longer supported.
1 VM-deployment supported
2 With the release of QuerySurge 8.1 (11/2020) only 64 bit deployment architectures only are supported.
3 Full Linux install required (minimal install not supported)
4 Disk space is critical for both data storage and data analysis engine
5 Solid-state drives (SSD), where available, are recommended over HDD drives, to enhance performance
2. Trial/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 trial deployment environment.
Single Server Setup (Trial/POC)
Component1 | Installation | Supported Operating Systems (64-bit)2,a |
CPU | Memory | Disk I/O | Disk Space4 |
QuerySurge (Application server, Database server) |
App & Database server installed on single desktop or server |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/83; Fedora core 20-363 |
4 cores minimum |
16 GB minimum |
Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.)5 |
minimum of 1 TB |
QuerySurge Agent | Installed on separate desktop(s) to alleviate resource contention |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/83; Fedora core 20-363 |
2 cores | 4 GB | N/A | 20 GB |
a RHEL 6 - EOL as of 11/30/20 and is no longer supported.
1 VM-deployment supported
2 With the release of QuerySurge 8.1 (11/2020) only 64 bit deployment architectures (x86_64) only are supported.
3 Full Linux install required (minimal install not supported)
4 Disk space is critical for both data storage and data analysis engine
5 Solid-state drives (SSD), where available, are recommended over HDD drives, to enhance performance
6 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).
3. Production Installation - Minimum Deployment System Requirements
Single Server Setup
Component1,2 | Installation | Supported Operating Systems (64-bit)3,a |
CPU | Memory | Disk I/O | Disk Space5 |
QuerySurge (Application server, Database server)2 |
App & Database server installed on single desktop or server |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
4 cores | 16 GB | Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.)6 |
1 TB |
QuerySurge Agent |
Installed on separate desktop(s) to alleviate resource contention |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
2 cores | 4 GB | Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,7 in which case maximum IOPS is recommended. | 20 GB |
a RHEL 6 - EOL as of 11/30/20 and is no longer supported.
1 VM-deployment supported
2 Server hardware/OS recommended
3 With the release of QuerySurge 8.1 (11/2020) only 64 bit deployment architectures (x86_64) only are supported
4 Full Linux install required (minimal install not supported)
5 Disk space is critical for both data storage and data analysis engine
6 Solid-state drives (SSD), where available, are recommended over HDD drives, to enhance performance
7 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; e) Avro file data
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 trial deployment environment.
Single Server Setup
Component1,2 | Installation | Supported Operating Systems (64-bit)3,a |
CPU | Memory | Disk I/O | Disk Space5 |
QuerySurge (Application server, Database server)2 |
App & Database server installed on single desktop or server |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
8 cores minimum |
32 GB minimum |
Maximum IOPS for the QuerySurge infrastructure available(e.g. Azure, AWS, on-prem, etc.)6 | minimum of 1 TB --------------- optional data storage drive8 |
QuerySurge Agent |
Installed on separate desktop(s) to alleviate resource contention |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
2 cores | 8 GB | Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,7 in which case maximum IOPS is recommended | 20 GB |
a RHEL 6 - EOL as of 11/30/20 and is no longer supported.
1 VM-deployment Supported
2 Server hardware/OS recommended
3 With the release of QuerySurge 8.1 (11/2020) only 64 bit deployment architectures (x86_64) only are supported
4 Full Linux install required (minimal install not supported)
5 Disk space is critical for both data storage and data analysis engine
6 Solid-state drives (SSD), where available, are recommended over HDD drives, to enhance performance
7 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; e) Avro file data
8 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
Component1,2 | Installation | Supported Operating Systems (64-bit)3,a |
CPU | Memory | Disk I/O | Disk Space5 |
QuerySurge Application server2 |
Installed on separate desktop or server to alleviate resource contention |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
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 server2 | Installed on separate desktop or server to alleviate resource contention |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
4 cores | 16 GB | Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.)6 | 1 TB |
QuerySurge Agent |
Installed on separate desktop(s) to alleviate resource contention |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
2 cores | 8 GB | Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,7 in which case maximum IOPS is recommended | 20 GB |
a RHEL 6 - EOL as of 11/30/20 and is no longer supported.
1 VM-deployment Supported
2 Server hardware/OS recommended
3 With the release of QuerySurge 8.1 (11/2020) only 64 bit deployment architectures (x86_64) only are supported
4 Full Linux install required (minimal install not supported)
5 Disk space is critical for both data storage and data analysis engine
6 Solid-state drives (SSD), where available, are recommended over HDD drives, to enhance performance
7 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; e) Avro file data
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 trial deployment environment.
Multi-Server Setup
Component1,2 | Installation | Supported Operating Systems (64-bit)3,a |
CPU | Memory | Disk I/O | Disk Space5 |
QuerySurge Application server2 |
Installed on separate desktop or server to alleviate resource contention |
Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
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 server2 | Installed on separate desktop or server to alleviate resource contention |
Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
8 cores minimum |
32 GB minimum |
Maximum IOPS for the QuerySurge infrastructure available (e.g. Azure, AWS, on-prem, etc.)6 | minimum of 1 TB --------------- optional data storage drive8 |
QuerySurge Agent |
Installed on separate desktop(s) to alleviate resource contention |
Windows 10 Windows Server: 2012/2012 R2/2016/2019; RHEL 7/84; Fedora core 20-364 |
2 cores | 8 GB | Agents are generally not Disk I/O sensitive. Some setups, however, are Disk I/O sensitive,7 in which case maximum IOPS is recommended | 20 GB |
a RHEL 6 - EOL as of 11/30/20 and is no longer supported.
1 VM-deployment Supported
2 Server hardware/OS recommended
3 With the release of QuerySurge 8.1 (11/2020) only 64 bit deployment architectures (x86_64) only are supported
4 Full Linux install required (minimal install not supported)
5 Disk space is critical for both data storage and data analysis engine
6 Solid-state drives (SSD), where available, are recommended over HDD drives, to enhance performance
7 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; e) Avro file data
8 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)
Note: In-place Operating System upgrades are not supported. If you are planning an in-place upgrade, please contact QuerySurge support prior to your upgrade for information.
Please feel free to reach out to us for further questions on your QuerySurge setup.
*** These requirements are subject to change without notice. ***
Comments
0 comments
Please sign in to leave a comment.