Virtual ViewX Server Configuration and Performance Guidelines
System performance is affected by many factors. When setting up the Virtual ViewX clients and servers on your system, you should take into account the Virtual ViewX related content in the following topics:
The table below shows the results of a series of industry-standard system benchmark tests that have been performed on a variety of Virtual ViewX client and server setups. We include the table here purely as a guideline and not as a guarantee of system performance. The Cores, RAM, and Graphics Architecture entries refer to the configuration of the machine on which the Virtual ViewX server is installed. The Network Bandwidth column shows the minimum rate of data transfer required between the Virtual ViewX server and the rest of the network.
Before using Virtual ViewX in a 'live' system, we recommend that you perform your own tests using a test system that accurately reflects the real system (including database size and data retrieval frequency). Perform further tests once Virtual ViewX is set up on the real system and whenever further Virtual ViewX clients are added.
Number of Virtual ViewX Clients per Server *1 *3 *4 |
CPU PassMark® *2 |
2D Graphics PassMark® | Cores | RAM | Graphics Architecture | Network Bandwidth |
---|---|---|---|---|---|---|
2 | 1800 | 200 | 4 | 4 GB | DirectX 11 or later with Windows Display Driver Model (WDDM) 1.2 or above | 100 MB |
5 |
4500 |
200 | 4 | 8 GB | 100 MB | |
10 |
8000 |
200 | 8 | 16 GB | 100 MB | |
15 |
10000 |
200 | 8 | 32 GB | 1 GB | |
20 |
15000 |
300 | 10 | 32 GB | 1 GB |
Notes:
*1 - This table is provided as a guide and not as a guarantee of system performance.
*2 - PassMark® ratings are suggested minimums. Lower values might be countered by higher marks in other areas.
*3 - Performance of Virtual ViewX might be affected by the complexity of any Mimics that are on display, including the data retrieval frequency of database items on those Mimics.
*4 - A second simultaneous Virtual ViewX session for the same user (for example, a second browser tab or second browser connected to the same server) counts as a separate Virtual ViewX client for performance purposes. However, as far as licenses are concerned, a second simultaneous Virtual ViewX session for the same user is included within the license of a single Virtual ViewX client.