2 Requirements

HP SAM Hardware and Software Requirements

Architectural Considerations and Best Practices for Setting up an HP SAM Environment

Server Sizing

In general, the HP SAM Server can handle a theoretical maximum user and resource population of 40,000.

This is based on the assumption that no more than 1% of users will attempt to connect within the same 30-second window.

HP SAM Server, at minimum specification, has been shown to handle up to at least 500 blade requests within the same 3-second time slot without giving a denial. The results may vary based on the speed of the servers and infrastructure used.

Increase Memory as user population grows:

Performing HP SAM searches can tax memory because the HP SAM Server pulls a copy of the database across the network to memory in order to complete this task.

One GB of RAM per 2,000 users or resources (whichever is greater) is a good rule of thumb. Increase processor speed and cores as user population grows.

Memory is the primary gate on performance of the HP SAM Server. When handling large user populations, the HP SAM Server has to search through the large database to get profiles and resource assignments. Once the memory hurdle is cleared, the next gate in performance is the processor.

2,000 Users/CPU Core is a reasonable rule of thumb.

Network I/O performance is not typically a bottleneck.

Extra NIC cards to handle higher load of users are not typically needed.

SQL Database Considerations

The HP SAM SQL database can be installed on the same server as the HP SAM Web Server to keep from buying another hardware platform and another Server OS license, however HP recommends separating them onto two different servers for the following reasons:

Recovery times from hardware failures will be faster.

As deployments grow in size and number of locations, there will likely be multiple HP SAM Web Servers but only one centralized HP SAM SQL database.

12 Chapter 2 Requirements