Motorola MC3090G Integration Guide - Page 118

Storage, Random Access Memory, Volatile File Storage (Cache Disk)

Get Motorola MC3090G - Win CE 5.0 Core PDF manuals and user guides View all Motorola MC3090G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 118 highlights

5 - 8 MC3000 Integrator Guide SampleCpy.xml Storage Mobile 6.1 contains three types of file storage: • Random Access Memory (RAM) • Persistent Storage • Application folder. Random Access Memory Executing programs use RAM to store data. Data stored in RAM is lost upon a warm boot. RAM also included a volatile file storage area called Cache Disk. Volatile File Storage (Cache Disk) Windows Mobile 6.1 memory architecture uses persistent storage for all files, registry settings, and database objects to ensure data is retained even after a power failure. Persistent storage is implemented using Flash memory technology which is generally slower than volatile RAM memory. In certain situations the speed of the operation is more important than the integrity of the data. For these situations, Motorola has provided a small volatile File Storage volume, accessed as the Cache Disk folder. Disk operations to the Cache Disk folder are much faster than to any of the persistent storage volumes, but data is lost across warm boots and power interruptions. Note that a backup battery powers RAM memory, including the Cache Disk, when you remove the main battery for a short period of time. The MC3000 uses the Cache Disk for temporary data that can be restored from other sources, for example, for temporarily "caching" HTML web pages by a browser or generating formatted files to send to a printer. Both situations benefit from the increased speed of the cache disk, but you can restore the data if needed. DO NOT use the Cache Disk as a method to improve application performance. Analyze applications that perform slower in persistent storage to optimize disk access. Common areas for optimization include minimizing the number of reads and writes to a file, removing unneeded debug logging, and minimizing file flushing or closing files.

  • 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
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
5 - 8
MC3000 Integrator Guide
SampleCpy.xml
<wap-provisioningdoc>
<characteristic type= “FileOperation”>
<characteristic type= “\Windows” translation= “filesystem”>
<characteristic type= “MakeDir”/>
<characteristic type= “example.txt” translation= “fileystem”>
<characteristic type= “Copy”>
<parm name= “Source” value= “\Application\example.txt” translation= “filesystem”/>
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Storage
Mobile 6.1 contains three types of file storage:
•
Random Access Memory (RAM)
•
Persistent Storage
•
Application folder.
Random Access Memory
Executing programs use RAM to store data. Data stored in RAM is lost upon a warm boot. RAM also included a
volatile file storage area called
Cache Disk
.
Volatile File Storage (Cache Disk)
Windows Mobile 6.1 memory architecture uses persistent storage for all files, registry settings, and database
objects to ensure data is retained even after a power failure. Persistent storage is implemented using Flash
memory technology which is generally slower than volatile RAM memory. In certain situations the speed of the
operation is more important than the integrity of the data. For these situations, Motorola has provided a small
volatile File Storage volume, accessed as the
Cache Disk
folder. Disk operations to the
Cache Disk
folder are
much faster than to any of the persistent storage volumes, but data is lost across warm boots and power
interruptions. Note that a backup battery powers RAM memory, including the
Cache Disk
, when you remove the
main battery for a short period of time.
The MC3000 uses the
Cache Disk
for temporary data that can be restored from other sources, for example, for
temporarily “caching” HTML web pages by a browser or generating formatted files to send to a printer. Both
situations benefit from the increased speed of the cache disk, but you can restore the data if needed.
DO NOT use the
Cache Disk
as a method to improve application performance. Analyze applications that perform
slower in persistent storage to optimize disk access. Common areas for optimization include minimizing the
number of reads and writes to a file, removing unneeded debug logging, and minimizing file flushing or closing
files.