HP BladeSystem bc2800 Administrator's Guide HP Session Allocation Manager (HP - Page 21

Requirements, HP SAM Hardware and Software Requirements, Architectural Considerations and Best

Get HP BladeSystem bc2800 - Blade PC PDF manuals and user guides View all HP BladeSystem bc2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

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. ENWW HP SAM Hardware and Software Requirements 13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
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.
ENWW
HP SAM Hardware and Software Requirements
13