配8300呀.

8300的客户就没我什么事情了，我们能卖掉8100低配已经不错了

8100也是IBM的事呀.
反正IBM的事,我们也有机会折腾啦.

DS8000如果还是固守着由IBM自己来卖，好多单子都拼不过USP VM、DMX4-950的

连DMX3-950也拼不过，连DMX1000也拼不过。


因为它太胖了。

看策略了。存储也就Cache能卖个好价钱，就好像6000里面的内存价格一样。
有时候，license更贵。

是的  hp也一样，多一倍cache基本就翻倍了..  license在中低端存储上基本就是半个存储了

8100每个控制器有好像是有8个内存槽?，32G cache每个内存槽正好插1个2G，这样成本比较低。换到单根4G成本会高不少，不过IBM价格也太离谱了,cache的list价格是原来的4倍!

Note: In a cluster environment, you need a single path to the each of the controllers (A and
B) of the DS4000. However, if the cluster software and host application can do persistent
reservations, you can keep multiple paths and the multipath driver will route the I/O request
using the appropriate path to the reserved logical drive.

In a single server environment, AIX is the other OS that allows load sharing (also called load
balancing). However, the best practice is not to use load balancing in AIX, as it can have
performance issues and cause disk thrashing.

Queue depth
The queue depth is the maximum number of commands that can be queued on the system at
the same time.
The DS4000 controller firmware version 05.30.xx.xx or earlier, the queue depth is 512; for the
DS4000 controller firmware Versions 06.1x.xx.xx or 05.4x.xx.xx, the queue depth is 2048.
This is represents 1024 per controller.

The formula for the correct queue depth on the host HBA for this level of firmware code is:
2048 / (number of hosts * LUNs per host)
For example, a system with four hosts, each with 32 LUNs, would have a maximum queue
depth of 16: 2048 / (4 * 32) = 16.
This setting should be set on each host bus adapter. See also 4.3.1, “Host based settings” on
page 136.
For Qlogic based HBAs the queue depth is known as execution throttle, this can be set with
either Qlogic SANSurfer or in the BIOS of the Qlogic-based HBA by pressing Ctl+Q during
the boot process.