IBM TS7700 Release 5.1 Performance White Paper Version 2.0
Page
6
© Copyright 2020 IBM Corporation
Peak and Sustained Write Throughput.
For all TS7770T
cp1->7
measurements, any previous workloads have been allowed
to quiesce with respect to pre-migration to backend tape and replication to other
clusters in the grid. In other words, the test is started with the grid in an idle state.
Starting with this initial idle state, data from the host is first written into the
TS7770T
cp1->7
disk cache with little if any premigration activity taking place. This
allows for a higher initial data rate and is termed the “peak” data rate. Once a pre-
established threshold is reached of non-premigrated compressed data, the
amount of premigration is increased, which can reduce the host write data rate.
This threshold is called the premigration priority threshold (PMPRIOR), and has
default value of 1600 gigabytes (GB). When a second threshold of non-
premigrated compressed data is reached, the incoming host activity is actively
throttled to allow for increased premigration activity. This throttling mechanism
operates to achieve a balance between the amount of data coming in from the
host and the amount of data being copied to physical tape. The resulting data
rate for this mode of behavior is called the “sustained” data rate, and could
theoretically continue on forever, given a constant supply of logical and physical
scratch tapes. This second threshold is called the premigration throttling
threshold (PMTHLVL) and has a default value of 2000 gigabytes (GB). These two
thresholds can be used in conjunction with the peak data rate to project the
duration of the peak period. Note that both the priority and throttling thresholds
can be increased or decreased via a host command line request. For all the run
in this white paper, PMPRIOR and PMTHLVL were set to 3600 and 4000
respective to achieve a longer peak duration.
For all TS7770C
cp1->7
measurements, CLDPRIOR was set to 3600 to establish the
cloud premigration priority threshold. The premigration throttle threshold was
determined by the number the FC5274 installed. I only installed 4 FC5274 so that
there were reasonable peak and sustained periods in a 6-hour run).
Read-hit and Recall Throughput
Similar to write activity, there are two types of TS7770T
cp1->7
(or TS7770C
cp1->7
)
read performance: “read-hit” (also referred to as “peak”) and “recall” (also referred
to as “read-miss”). A read hit occurs when the data requested by the host is
currently in the local disk cache. A recall occurs when the data requested is no
longer in the disk cache and must be first read in from physical tape (or from the
cloud). Read-hit data rates are typically higher than recall data rates.
TS7770T
cp1->7
recall performance is dependent on several factors that can vary
greatly from installation to installation, such as number of physical tape drives,
spread of requested logical volumes over physical volumes, location of the logical
volumes on the physical volumes, length of the physical media, and the logical
volume size. Because these factors are hard to control in the laboratory
environment, recall is not part of lab measurement.
TS7770C
cp1->7
recall was not included in this white paper.