全部

1·We distributed the DASD for the user mail boxes over these mount points.

我们将用于用户邮件箱的DASD分布在这些挂载点上。

2·This saves you from using up a real device and on DASD tracking and management.

这可以防止用完实际的设备，同时节省DASD跟踪和管理的开销。

3·DASD is cheap, and the time on the wire might be only a small part of the total time in the process.

DASD是便宜的，并且线路上的时间可能仅是过程中总时间的一小部分。

4·This is achieved by using a transactional log, based on a recoverable media (such as physical DASD).

通过使用基于可恢复介质（例如物理的 DASD）的事务日志来完成这个目标。

5·Such designs not only waste DASD space, but also require higher resource consumption for many DB2 operations.

这种设计不仅浪费DASD空间，而且，对于很多DB 2操作，还需要消耗更多的资源。

6·Also, we added four more CPs, increased the memory to 26 GB, and added more DASD to support the full user load.

而且，我们又增加了4个CP，将内存增加到26 GB，并增加更多DASD，以支持全部用户负载。

7·The more often that the data requested by applications is in memory rather than out on DASD, the better overall performance will be.

应用程序所请求的数据出现在内存中（而不是外面的 DASD 上）的概率越大，总体性能就越好。

8·The total direct access storage device (DASD) attached to this physical system, through its various fiber channels, was well over 200 TB.

通过不同光纤连接到这个物理系统上的直接访问存储设备(DASD)加起来超过200 TB。

9·Let's simulate this scenario, assuming that objects stay six months in DASD, three years in external storage, and seven years in tapes.

让我们来模拟一下这个场景，假设对象在DASD中存储6个月，在外部存储中存储3年，在磁带中存储7年。

10·For the Lotus Domino workload, we ended up with about 20 TB of DASD attached to this one Linux kernel, defined as extended count key data (ECKD) devices.

对于Lotus Domino工作负载，根据extended count key data (ECKD)设备的定义，我们最终有大约20 TB的DASD连接到这一个Linux内核。