30.11.2012 Views

FICON Express2 Channel Performance Version 1.0 - IBM

FICON Express2 Channel Performance Version 1.0 - IBM

FICON Express2 Channel Performance Version 1.0 - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>FICON</strong> <strong>Express2</strong> <strong>Channel</strong> <strong>Performance</strong> <strong>Version</strong> <strong>1.0</strong><br />

Page 16<br />

Figure 16 is the response time components for the 27k read hit benchmark. Because of the<br />

large 27k block size, CONNECT time is the largest component of the total response time. As<br />

link utilizations (LU) increase, CONNECT time increases first by one tenth of a millisecond,<br />

and then PEND time also increases by one tenth of a millisecond. At 80% LU, both<br />

CONNECT time and PEND time are 0.4ms higher than they were at 10% LU, another<br />

indicator that this workload is in the middle of the two extremes defined by processor limited<br />

workloads such as the 4K bytes per I/O benchmarks and bus or link limited workloads such<br />

as the 6x27K bytes per I/O benchmarks.<br />

response time components for 27K read hits...<br />

27K bytes/io, 100% cu cache hit ratio<br />

2Gbps Link Utilization(LU)<br />

10% LU<br />

20% LU<br />

30% LU<br />

40% LU<br />

50% LU<br />

60% LU<br />

70% LU<br />

80% LU<br />

0 0.5 1 1.5 2<br />

response times in ms<br />

Figure 16<br />

pend<br />

conn<br />

The 32x4k read hit benchmark depicted in Figure 17 is another benchmark that pushes both<br />

the processor and the link to high levels of utilization with the processor slightly higher than<br />

the link utilization. Figure 17 shows the response time components for a 32x4K read hit<br />

benchmark which is a long chain of short blocks. Here CONNECT time is the largest<br />

component since the total data transfer size is 128K bytes per I/O even though the block size<br />

for each CCW is only 4K bytes. Since there is a separate CCW for each of the 4K bytes and<br />

the <strong>FICON</strong> <strong>Express2</strong> channel processor works on each CCW separately, the processor gets<br />

pushed to high utilization levels for this workload. With this benchmark, CONNECT time<br />

starts out at a little over 2ms at 10% <strong>FICON</strong> Processor utilization (FPU) and increases to over<br />

3ms at 60% FPU, when just under 120MB/sec are being transferred, which represents about<br />

60% link utilization as well.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!