Difference between revisions of "Vital Signs Windows Server Recommendations"
(→Shared Systems) |
|||
| Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
| − | + | Vital Signs has the potential to capture and manipulate hundreds of millions of rows of data on a daily basis. This volume of data requires a robust server environment to support it with acceptable performance to the end user. | |
| − | on a daily basis. This volume of data requires a robust server environment to support it with | ||
| − | acceptable performance to the end user. | ||
==Recommended Minimum Configuration== | ==Recommended Minimum Configuration== | ||
| − | + | Based on membership, the following should serve as a reasonable guide for producing a capable Vital Signs host server | |
| − | producing a capable Vital Signs host server | ||
'''Membership Size: 0 – 50k members''' | '''Membership Size: 0 – 50k members''' | ||
| Line 30: | Line 27: | ||
==Shared Systems== | ==Shared Systems== | ||
| − | + | For clients with a member base greater than 50k we highly recommend using a standalone system for the Vital Signs environment. Shared systems can cause undesired memory complications during heavy load times. | |
==Virtual Environments== | ==Virtual Environments== | ||
| − | + | We recommend when running a virtual environment, that the host be capable of the minimum requirements stated above at peak load times. The virtualization performance hit, especially with hard drive throughput, must be considered when designing the system for maximum long term performance. | |
| − | minimum requirements stated above at peak load times. The virtualization performance hit, | ||
| − | especially with hard drive throughput, must be considered when designing the system for maximum | ||
| − | long term performance. | ||
==Multi Threaded performance== | ==Multi Threaded performance== | ||
| − | + | Vital Signs is powered by QlikView Server, which is capable of utilizing up to 64 processors. The server performance will greatly benefit from a multi core system. Processor affinity can be selected in the QlikView Server Control Console area in the scenario of a shared system. | |
| − | processors. The server performance will greatly benefit from a multi core system. Processor | ||
| − | affinity can be selected in the Server Control Console area in the scenario of a shared system. | ||
Revision as of 20:32, 13 September 2012
Contents
Overview
Vital Signs has the potential to capture and manipulate hundreds of millions of rows of data on a daily basis. This volume of data requires a robust server environment to support it with acceptable performance to the end user.
Recommended Minimum Configuration
Based on membership, the following should serve as a reasonable guide for producing a capable Vital Signs host server
Membership Size: 0 – 50k members CPU : Dual 2.4ghz + * Memory : 8 GB + Hard Drive Throughput (read/write): 50MB/s + Storage Space : 100GB + OS : 64bit Standard Server 2003 + / 64bit Standard Server 2008 + Member Base: 51 – 150k members Recommended Minimum Configuration CPU : Quad 2.4ghz + * Memory : 16GB + Hard Drive Throughput (read/write): 100MB/s + Storage Space : 250GB + OS : 64bit Standard Server 2003 + / 64bit Standard Server 2008 +
Note: must be 64bit non Itanium processors
For clients with a member base greater than 50k we highly recommend using a standalone system for the Vital Signs environment. Shared systems can cause undesired memory complications during heavy load times.
Virtual Environments
We recommend when running a virtual environment, that the host be capable of the minimum requirements stated above at peak load times. The virtualization performance hit, especially with hard drive throughput, must be considered when designing the system for maximum long term performance.
Multi Threaded performance
Vital Signs is powered by QlikView Server, which is capable of utilizing up to 64 processors. The server performance will greatly benefit from a multi core system. Processor affinity can be selected in the QlikView Server Control Console area in the scenario of a shared system.
