Adaptec 133U2 User Guide - Page 135

Read Caching

Page 135 highlights

Managing Arrays and Spares 10 Click Save to save the new performance setting. The changes are not written to disk until you exit the application. If a new performance setting has been successfully created, it will appear in the Optimize Performance for list box. 11 When the Optimize Performance dialog box displays, click OK to save your changes. Read Caching There are two types Read caches: the Demand Cache and the Lookahead Cache. Options for these caches can be adjusted separately for each array. s Demand Caching- this defines the maximum Read command size (stated as a number of data blocks) that will be cached. Demand Caching can greatly improve I/O performance if your application typically reads data and then reads it again soon afterwards. For example, if Demand Caching is set to 4 blocks and the operating system issues a Read command for 4 blocks of data, all of the demand data is cached. however, if the operating system issues a Read command for 5 (or more) blocks of data, none of the demand data is cached. s Look-ahead Caching Factor - this factor is a multiplier to the command size that defines the maximum number of data blocks that will be stored in the Look-ahead Cache in addition to the amount of data requested by the Read command. Lookahead caching can greatly improve I/O performance if your application typically reads data in sequential blocks. For example, if the Look-ahead Caching factor is set to 16 and the operating system issues a Read command, the demand data is cached if the command is less than or equal to 4 blocks, and the next (sequential) 16 x 4 blocks of data is stored in the Lookahead Cache. 10-11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174

10-11
Managing Arrays and Spares
10
Click
Save
to save the new performance setting. The changes
are not written to disk until you exit the application. If a new
performance setting has been successfully created, it will
appear in the
Optimize Performance for
list box.
11
When the Optimize Performance dialog box displays, click
OK
to save your changes.
Read Caching
There are two types Read caches: the Demand Cache and the Look-
ahead Cache. Options for these caches can be adjusted separately for
each array.
Demand Caching
— this defines the maximum Read
command size (stated as a number of data blocks) that will be
cached. Demand Caching can greatly improve I/O
performance if your application typically reads data and then
reads it again soon afterwards. For example, if Demand
Caching is set to 4 blocks and the operating system issues a
Read command for 4 blocks of data, all of the demand data is
cached. however, if the operating system issues a Read
command for 5 (or more) blocks of data, none of the demand
data is cached.
Look-ahead Caching Factor
— this factor is a multiplier to the
command size that defines the maximum number of data
blocks that will be stored in the Look-ahead Cache in addition
to the amount of data requested by the Read command. Look-
ahead caching can greatly improve I/O performance if your
application typically reads data in sequential blocks. For
example, if the Look-ahead Caching factor is set to 16 and the
operating system issues a Read command, the demand data is
cached if the command is less than or equal to 4 blocks, and the
next (sequential) 16 x 4 blocks of data is stored in the Look-
ahead Cache.