IBM 86884RX Installation Guide - Page 50

Explicitly Parallel, Instruction Computing

Page 50 highlights

scalable IA-32-based server, which has become a well-accepted and tested solution in medium to large enterprises. A replacement to the xSeries 380, the first xSeries server with a 64-bit architecture targeted, tested, and proven by software and hardware developers. Unlike competitors without such background, IBM put many years of invaluable experience with 64-bit technology (IBM pSeries™ and zSeries™ servers) into the development of the x450. All of these advantages make the xSeries 450 production enterprise-level server a viable alternative to RISC-based architectures, while protecting many years of investments and knowledge gained from IA-32 platform development. Intel expects the Itanium Architecture to be a product base for the next 25 years or more. The Itanium 2 processor used in the x450 is based on the Explicitly Parallel Instruction Computing (EPIC) architecture, which incorporates a number of new technologies, features, and capabilities that make it ideal for the high-end server and workstation markets. EPIC allows users to take advantage of its large memory addressability and parallel execution capabilities. The chip also supports intelligent prediction and speculation of events to deduce redundancy and improve performance. The Itanium's floating point engine enhances performance for complex computations that are required for data-mining, scientific, and technical applications. The Itanium 2 processor is the second in a family of Intel enterprise-class processors. For more information about the Intel Itanium 2 processor, see: http://www.intel.com/products/server/processors/server/itanium2/ Intel Itanium Architecture-based microprocessors have the following features: Advanced parallelism High performance requires parallel execution, which is either very limited or hardly achieved in today's architecture. The traditional PC systems are not designed for parallelism, which is critical for current demanding applications (for example databases and application servers). Today's processors using limited parallelism are often 60% idle. When source code is compiled on today's systems, the result of the compilation is sequential machine code. A regular (non-Itanium processor family) compiler takes sequential code and examines and optimizes it for parallelism but then has to regenerate sequential code, but in such a way that the processor can re-extract the parallelization from it. The processor will then be required to read this implied parallelism from the machine code, re-build it, and execute it. 36 IBM ^ xSeries 450 Planning and Installation Guide

  • 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
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

36
IBM
^
xSeries 450 Planning and Installation Guide
scalable IA-32-based server, which has become a well-accepted and tested
solution in medium to large enterprises.
±
A replacement to the xSeries 380, the first xSeries server with a 64-bit
architecture targeted, tested, and proven by software and hardware
developers.
±
Unlike competitors without such background, IBM put many years of
invaluable experience with 64-bit technology (IBM pSeries™ and zSeries™
servers) into the development of the x450.
All of these advantages make the xSeries 450 production enterprise-level server
a viable alternative to RISC-based architectures, while protecting many years of
investments and knowledge gained from IA-32 platform development.
Intel expects the Itanium Architecture to be a product base for the next 25 years
or more.
The Itanium 2 processor used in the x450 is based on the
Explicitly Parallel
Instruction Computing
(EPIC) architecture, which incorporates a number of new
technologies, features, and capabilities that make it ideal for the high-end server
and workstation markets. EPIC allows users to take advantage of its large
memory addressability and parallel execution capabilities. The chip also supports
intelligent prediction and speculation of events to deduce redundancy and
improve performance. The Itanium's floating point engine enhances performance
for complex computations that are required for data-mining, scientific, and
technical applications.
The Itanium 2 processor is the second in a family of Intel enterprise-class
processors. For more information about the Intel Itanium 2 processor, see:
Intel Itanium Architecture-based microprocessors have the following features:
±
Advanced parallelism
High performance requires parallel execution, which is either very limited or
hardly achieved in today's architecture. The traditional PC systems are not
designed for parallelism, which is critical for current demanding applications
(for example databases and application servers).
Today’s processors using limited parallelism are often 60% idle. When source
code is compiled on today’s systems, the result of the compilation is
sequential machine code. A regular (non-Itanium processor family) compiler
takes sequential code and examines and optimizes it for parallelism but then
has to regenerate sequential code, but in such a way that the processor can
re-extract the parallelization from it. The processor will then be required to
read this implied parallelism from the machine code, re-build it, and execute it.