HP NetServer AA 4000 HP AA HP Netserver 4000 Reference Guide - Page 15

The Compute Elements, The SSDLs, The I/O Processors

Get HP NetServer AA 4000 PDF manuals and user guides View all HP NetServer AA 4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 15 highlights

Ch 1: Architecture Overview and Terminology Division of Labor The compute elements and the I/O processors have very distinct roles and therefore have different performance characteristics. If the array was going to do nothing more than run Windows NT without any applications, then the memory requirements are minimal. The array can be functional with 64 MB of memory for each node. This serves to prove that the AA 4000 software itself is not memory intensive and does require a significant amount of server resources. The Compute Elements The compute element functions with just the CPU and the memory. The server is sized for the maximum amounts of CPU and memory required for the application that stays within the limits of the memory support of the physical server and the fact that the HP AA 4000 software currently supports one CPU and a maximum of 2 GB of system memory. The system will generate I/O requests, but they are immediately intercepted by the HP AA 4000 software and transferred to the IOP via the MICs, cables, and SSDLs. This creates a very low overhead for I/O operations on the CE. The SSDLs These two components are nothing more than I/O routers. By requiring that the nodes be attached to specific ports, what little software function there is in the SSDLs is easily maintained and does not have to be concerned with any kind of routing scheme or mesh. The SSDLs are for making sure the data is transferred from each CE to both IOPs by simply providing a path. The HP AA 4000 software is responsible for the integrity of the data between the nodes and largely does this through checksums (EDCs) at the end of each packet transfer. The I/O Processors Here a different kind of server activity takes place. The I/O Processors do not run any applications other than simple management software added by the customer. They are complex I/O controllers that for lack of an easier solution happen to be running Windows NT. They are not in lock-step with each other, but instead, maintain disk synchronization through a HP AA 4000 software disk partition on each logical disk the CE uses. These are not CPU or memory intensive operations. As it turns out, the disk activity itself, as in most optimized server environments, can be the bottleneck if there is one. CAUTION It is possible to run applications on the IOPs. However, this impacts the reliability of the overall system. HP strongly recommends that other applications not be run on the IOPs but will continue to support the array. Network Server Division 1-9

  • 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
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
Ch 1: Architecture Overview and Terminology
Network Server Division
1-9
Division of Labor
The compute elements and the I/O processors have very distinct
roles and therefore have different performance characteristics.
If the
array was going to do nothing more than run Windows NT without
any applications, then the memory requirements are minimal.
The
array can be functional with 64 MB of memory for each node.
This
serves to prove that the AA 4000 software itself is not memory
intensive and does require a significant amount of server resources.
The Compute Elements
The compute element functions with just the CPU and the memory.
The server is sized for the maximum amounts of CPU and memory
required for the application that stays within the limits of the
memory support of the physical server and the fact that the HP AA
4000 software currently supports one CPU and a maximum of 2 GB
of system memory.
The system will generate I/O requests, but they
are immediately intercepted by the HP AA 4000 software and
transferred to the IOP via the MICs, cables, and SSDLs.
This creates
a very low overhead for I/O operations on the CE.
The SSDLs
These two components are nothing more than I/O routers.
By
requiring that the nodes be attached to specific ports, what little
software function there is in the SSDLs is easily maintained and does
not have to be concerned with any kind of routing scheme or mesh.
The SSDLs are for making sure the data is transferred from each CE
to both IOPs by simply providing a path.
The HP AA 4000 software
is responsible for the integrity of the data between the nodes and
largely does this through checksums (EDCs) at the end of each
packet transfer.
The I/O Processors
Here a different kind of server activity takes place.
The I/O
Processors do not run any applications other than simple
management software added by the customer.
They are complex I/O
controllers that for lack of an easier solution happen to be running
Windows NT.
They are not in lock-step with each other, but instead,
maintain disk synchronization through a HP AA 4000 software disk
partition on each logical disk the CE uses.
These are not CPU or
memory intensive operations.
As it turns out, the disk activity itself,
as in most optimized server environments, can be the bottleneck if
there is one.
CAUTION
It is possible to run applications on the IOPs.
However, this
impacts the reliability of the overall system.
HP strongly
recommends that other applications not be run on the IOPs
but will continue to support the array.