Figure 2
A Well-Designed System
Lower
Performance
a b c de
a,b,c,d,e represent the performance capabilities
of each system component
Note that all components in a well-designed system are within the same range
of performance. But in this case, a less than optimum component is cost
effective. The components are so closely matched that upgrading the lower-
end component a would not increase performance enough to make it worth the
cost.
Figure 3
shows a poorly designed system with an inefficient mix of low- and
high-performance components.
Figure 3
A Poorly Designed System
Lower
Performance
f
g
f,g,h,i,j represent the performance capabilities
of each system component
In this system, components f and g have performance characteristics that are
considerably inferior to components h, i, and j. With component f as the
bottleneck, components h, i, j, and even g are constrained by f so that they run
much more slowly than their designs would otherwise permit. In this system,
the bottleneck is significantly hampering the system's performance.
This is a poorly designed system because the high-performance components
aren't able to perform anywhere near their full potential. In fact, because of
the high-performance characteristics of h, i, and j, this system might have cost
more than the system in
greater disparity between its low- and high-performance components.
Higher
Performance
Higher
Performance
h i j
Figure
3. But it cannot perform as well because of the
Optimizing the NetWare Server
35
Need help?
Do you have a question about the NETWARE 6-DOCUMENTATION and is the answer not in the manual?
Questions and answers