Difference between revisions of "Vital Signs Windows Server Recommendations"
>Johno (→Virtual Environments) |
|||
| (16 intermediate revisions by 4 users not shown) | |||
| Line 3: | Line 3: | ||
| − | |||
| − | + | ==Supported Windows Server Operating Systems== | |
| − | '''Membership Size: 0 – 50k members''' | + | <!--* 64bit Server 2003 (All editions) removed for obsolescence --> |
| − | CPU : | + | * 64bit Server 2008 (All editions) |
| + | * 64bit Server 2008 R2 (All editions) | ||
| + | * 64bit Server 2012 (All editions) | ||
| + | * 64bit Server 2012 R2 (All editions) | ||
| + | |||
| + | ==Recommended Minimum Hardware Configuration== | ||
| + | |||
| + | Based on membership, the following should serve as a reasonable guide for producing a capable Vital Signs host server. Since all sites are different, you may need additional resources in your environment. | ||
| + | |||
| + | '''Membership Size: 0 – 25k members''' | ||
| + | CPU : Quad 2.4ghz + * | ||
| + | Memory : 4 GB + | ||
| + | Hard Drive Throughput (read/write): 100MB/s + | ||
| + | Storage Space : 50GB + | ||
| + | |||
| + | '''Membership Size: 26 – 50k members''' | ||
| + | CPU : Quad 2.4ghz + * | ||
Memory : 8 GB + | Memory : 8 GB + | ||
| − | Hard Drive Throughput (read/write): | + | Hard Drive Throughput (read/write): 100MB/s + |
Storage Space : 100GB + | Storage Space : 100GB + | ||
| − | |||
'''Member Base: 51 – 150k members''' | '''Member Base: 51 – 150k members''' | ||
Recommended Minimum Configuration | Recommended Minimum Configuration | ||
| − | CPU : Quad 2.4ghz + * | + | CPU : 2 x Quad 2.4ghz + * |
Memory : 16GB + | Memory : 16GB + | ||
Hard Drive Throughput (read/write): 100MB/s + | Hard Drive Throughput (read/write): 100MB/s + | ||
Storage Space : 250GB + | Storage Space : 250GB + | ||
| − | + | ||
| + | '''Member Base: 250k+ members''' | ||
| + | Recommended Minimum Configuration | ||
| + | CPU : 4 x Quad 2.4ghz + * | ||
| + | Memory : 32GB + | ||
| + | Hard Drive Throughput (read/write): 100MB/s + | ||
| + | Storage Space : 500GB + | ||
| + | |||
| + | ''* Note: must be NON Itanium processors'' | ||
| − | + | ==Server Performance Recommendations== | |
| + | * Hard drive throughput (read/write): 100MB/s+ | ||
| + | * Disable hyper threading | ||
| + | * Enable node interleaving (Numa disabled) | ||
| + | * Power management (power profile) Max performance | ||
==Shared Systems== | ==Shared Systems== | ||
| − | For clients with a member base greater than 50k we | + | For clients with a member base greater than 50k we 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. | 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== | ==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. | 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. | ||
Latest revision as of 18:23, 15 January 2016
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.
Supported Windows Server Operating Systems
- 64bit Server 2008 (All editions)
- 64bit Server 2008 R2 (All editions)
- 64bit Server 2012 (All editions)
- 64bit Server 2012 R2 (All editions)
Recommended Minimum Hardware Configuration
Based on membership, the following should serve as a reasonable guide for producing a capable Vital Signs host server. Since all sites are different, you may need additional resources in your environment.
Membership Size: 0 – 25k members CPU : Quad 2.4ghz + * Memory : 4 GB + Hard Drive Throughput (read/write): 100MB/s + Storage Space : 50GB + Membership Size: 26 – 50k members CPU : Quad 2.4ghz + * Memory : 8 GB + Hard Drive Throughput (read/write): 100MB/s + Storage Space : 100GB + Member Base: 51 – 150k members Recommended Minimum Configuration CPU : 2 x Quad 2.4ghz + * Memory : 16GB + Hard Drive Throughput (read/write): 100MB/s + Storage Space : 250GB + Member Base: 250k+ members Recommended Minimum Configuration CPU : 4 x Quad 2.4ghz + * Memory : 32GB + Hard Drive Throughput (read/write): 100MB/s + Storage Space : 500GB + * Note: must be NON Itanium processors
Server Performance Recommendations
- Hard drive throughput (read/write): 100MB/s+
- Disable hyper threading
- Enable node interleaving (Numa disabled)
- Power management (power profile) Max performance
For clients with a member base greater than 50k we 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.
