QMS Hardware Requirements

The recommended hardware for running the Recording Service (CRS) and the Media Processing Service (MPS) depends on the projected total number of simultaneous recordings. The recommended hardware for running the Data Service (DS) depends on the projected number of total users. For smaller deployments, it is possible to co-locate the DS, CRS and MPS on a single server. For larger deployments, the DS should be located on its own server and sized based on the total number of users in the system.

Calls Only (Co-Located DS, CRS and MPS)

LESS THAN 50 SIMULTANEOUS CALL RECORDINGS

  • Processor: Haswell 2.2 Ghz or better, 4 logical CPUs minimum

  • Memory: 4GB memory (minimum)

  • Disk used for QMS local storage locations:

    • SSD (recommended)

Calls Only (Co-Located CRS and MPS)

50 TO 100 SIMULTANEOUS CALL RECORDINGS (Dedicated Server)

  • Processor: Haswell 2.2 Ghz or better, 8 logical CPUs minimum

  • Memory: 4GB memory (minimum)

  • Disk used for QMS local storage locations:

    • 15k RPM drive (minimum)

    • SSD (recommended)

100 TO 250 SIMULTANEOUS CALL RECORDINGS (Dedicated Server)

  • Processor: Broadwell 2.3 Ghz or better, 16 logical CPUs minimum

  • Memory: 8GB memory (minimum)

  • Disk used for QMS local storage locations:

    • 15k RPM drive (minimum)

    • SSD (recommended)

250 TO 500 SIMULTANEOUS CALL RECORDINGS (Dedicated Server)

  • Processor: Broadwell 2.3 Ghz or better, 16 logical CPUs minimum

  • Memory: 16GB memory (minimum)

  • Disk used for QMS local storage locations:

    • 15k RPM drive (minimum)

    • SSD (recommended)

Call and Screen Recording (Co-Located CRS and MPS)

LESS THAN 25 SIMULTANEOUS CALL AND SCREEN RECORDINGS

  • Processor: Broadwell 2.3 Ghz or better, 8 logical CPUs minimum

  • Memory: 8GB memory (minimum)

  • Disk: used for QMS local storage locations:

    • 15k RPM drive (minimum)

    • SSD (recommended)

25 TO 50 SIMULTANEOUS CALL AND SCREEN RECORDINGS

  • Processor: Broadwell 2.3 Ghz or better, 16 logical CPUs minimum

  • Memory: 16GB memory (minimum)

  • Disk used for QMS local storage locations:

    • 15k RPM drive (minimum)

    • SSD (recommended)

Call and Screen Recording (Co-Located CRS and MPS)

50 TO 100 SIMULTANEOUS CALL AND SCREEN RECORDINGS (Dedicated Server)

  • Processor: Broadwell 2.3 Ghz or better, 32 logical CPUs minimum

  • Memory: 32GB memory (minimum)

  • Disk used for QMS local storage locations:

    • 15k RPM drive (minimum)

    • SSD (recommended)

100 TO 150 SIMULTANEOUS CALL AND SCREEN RECORDINGS (Dedicated Server)

  • Processor: Skylake 2.7 Ghz or better, 32 logical CPUs minimum

  • Memory: 32GB memory (minimum)

  • Disk used for QMS local storage locations:

    • 15k RPM drive (minimum)

    • SSD (recommended)

Call and Teams Video Call Recording:

Recording Teams video calls will require significantly more Media Processing resources than the normal QMS Screen Recording or Teams video desktop sharing session recordings. For recording Teams video calls, please refer to the QMS Sizing spreadsheet for suggested server sizes and configurations.

DataService (Dedicated Server):

Local SQL Server

LESS THAN 200 TOTAL USERS

  • Processor: Server class 4 logical cores minimum

  • Memory: 6 GB memory (minimum)

200 TO 500 TOTAL USERS

  • Processor: Server class 6 logical cores minimum

  • Memory: 8 GB memory (minimum)

OVER 500 TOTAL USERS

  • Separate SQL Server required

Remote SQL Server

LESS THAN 200 TOTAL USERS

  • Processor: Server class 4 logical cores minimum

  • Memory: 4 GB memory (minimum)

200 TO 500 TOTAL USERS

  • Processor: Server class 6 logical cores minimum

  • Memory: 6 GB memory (minimum)

500 TO 1000 TOTAL USERS

  • Processor: Server class 8 logical cores minimum

  • Memory: 8 GB memory (minimum)

OVER 1000 USERS

  • Contact Enghouse Interactive to discuss specifications

For deployments larger than those scoped out in this document, for deployments of Teams video call recording or for deployments where co-locating the Recording Service and Media Processing service is not desired, please refer to the QMS Sizing spreadsheet for suggested server sizes and configurations.

Logical CPU counts are calculated differently depending on deployment type:

  • Virtual servers: 1 virtual CPU assigned to server = 1 logical CPU

  • Physical servers with Hyper Threading: 1 physical CPU core = 2 logical CPUs

  • Physical server without Hyper Threading: 1 physical CPU core = 1 logical CPU

Full-Text Search (Solr Instances):

Sizing of Solr instances has no generic answer. It is very dependent on the size and number of searchable documents, as well as the criteria supplied to any given search query. The two main values taken into consideration when sizing a Solr instance are the amount of RAM needed for the Java JVM (Java heap), and the amount of OS Disk Cache available for indexes. As a starting point, based on 1,000,000 documents averaging 5 KB in size, the following values can be used:

  • RAM: 1 GB minimum

  • Disk space: 1 GB minimum

Please see the QMS Sizing spreadsheet to estimate using other document number and average size values.

The Java JVM encounters performance problems with heap sizes greater than 32 GB. RAM estimates above this number will require adding more Solr instances, preferably on separate physical hardware.

RAM estimates above 2 GB might experience performance degradation based on Java JVM garbage collection processing, and may require tuning of the garbage collector for a specific environment.