IBM DTCA-24090 Hard Drive Specifications - Page 83

To recover to Active mode from Active Idle requires about 40 ms. This does not represent

Get IBM DTCA-24090 - Travelstar 4.1 GB Hard Drive PDF manuals and user guides View all IBM DTCA-24090 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 83 highlights

Each time this algorithm decides that the current burst of commands is not yet complete, it places the device in Performance Idle mode. This means another command will arrive very soon, and the response to it can now be instantaneous without the delay associated with conventional idle. Since bursts usually contain tens of commands, performance is improved. When this algorithm decides the current burst of commands is complete, it knows with high probability that the next command will not occur for a relatively long time (seconds). To conserve power, this feature places the device in Active Idle mode, then performs a seek to the mid-band and enters a low power state. The optimal time to enter Active Idle is variable depending on the users recent behavior. It is not possible to achieve the same level of savings with a fixed entry time into Active Idle because every users data and access pattern is different. The optimum entry time changes over time. To recover to Active mode from Active Idle requires about 40 ms. This does not represent a significant performance impact because it is a relatively rare event, and because a new burst of commands almost always begins with a seek to a new location which requires the time anyway. Throughput is maintained because Active Idle is entered only when a long idle interval is anticipated. The same algorithm works for entering into Low Power Idle mode, which consumes less power and need more recovery time switching from this mode to Active mode. General Operation Descriptions 75

  • 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
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
Each time this algorithm decides that the current burst of commands is not yet complete, it places the device
in Performance Idle mode. This means another command will arrive very soon, and the response to it can
now be instantaneous without the delay associated with conventional idle. Since bursts usually contain tens
of commands, performance is improved.
When this algorithm decides the current burst of commands is complete, it knows with high probability that
the next command will not occur for a relatively long time (seconds). To conserve power, this feature places
the device in Active Idle mode, then performs a seek to the mid-band and enters a low power state.
The optimal time to enter Active Idle is variable depending on the users recent behavior.
It is not possible
to achieve the same level of savings with a fixed entry time into Active Idle because every users data and
access pattern is different.
The optimum entry time changes over time.
To recover to Active mode from Active Idle requires about 40 ms. This does not represent a significant
performance impact because it is a relatively rare event, and because a new burst of commands almost
always begins with a seek to a new location which requires the time anyway. Throughput is maintained
because Active Idle is entered only when a long idle interval is anticipated.
The same algorithm works for entering into Low Power Idle mode, which consumes less power and need
more recovery time switching from this mode to Active mode.
General Operation Descriptions
75