Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typo and clarify wording in the new faster-than-filesystem update. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
2912902889f80e4e1daaa1b35a617e2b |
| User & Date: | drh 2017-05-22 20:01:48 |
Context
|
2017-05-22
| ||
| 20:04 | Another typo in the faster than filesystem document. check-in: de15ebf872 user: drh tags: trunk | |
| 20:01 | Fix typo and clarify wording in the new faster-than-filesystem update. check-in: 2912902889 user: drh tags: trunk | |
| 19:38 | Fix another release note typo. check-in: 4020461a82 user: drh tags: trunk | |
Changes
Changes to pages/fasterthanfs.in.
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
...
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
|
<p>The table below shows data collected using [https://www.sqlite.org/src/file/test/kvtest.c|kvtest.c] on five different systems: An old Dell laptop running Windows7, a new Lenovo laptop running Windows10, a Mac-Pro, an Ubuntu desktop machine, and an older Android phone (a Galaxy S3). All machines use SSD except the Dell which has a hard-drive. The test database is 100K BLOBs uniformly distributed between 8K and 12K in size, each. The database page size is 4KiB. The chart shows average BLOB access time in microseconds. <center> <table border=1> <tr> <th>kvtest arguments <th>Win7 ................................................................................ Always remember: <i>Your mileage may vary</i>. Rerun these tests yourself on your own hardware using data that is a close match to your production data before drawing conclusions. <p> Notice that the individual file access times on Windows are dramatically slower than on the unix systems. This might be because the 100K BLOBs are all stored ina single directory and Windows is inefficient at searching directories with large numbers of files. The Windows file access times might be improved if the BLOBs were stored in a hierarchy of directories, rather than dumping them all into a single big directory. <h2>Key Points</h2> <ol> |
|
>
|
|
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
...
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
|
<p>The table below shows data collected using [https://www.sqlite.org/src/file/test/kvtest.c|kvtest.c] on five different systems: An old Dell laptop running Windows7, a new Lenovo laptop running Windows10, a Mac-Pro, an Ubuntu desktop machine, and an older Android phone (a Galaxy S3). All machines use SSD except the Dell which has a hard-drive. The test database is 100K BLOBs uniformly distributed between 8K and 12K in size, for a total about 1 gigabyte of content. The database page size is 4KiB. The chart shows average BLOB access time in microseconds. <center> <table border=1> <tr> <th>kvtest arguments <th>Win7 ................................................................................ Always remember: <i>Your mileage may vary</i>. Rerun these tests yourself on your own hardware using data that is a close match to your production data before drawing conclusions. <p> Notice that the individual file access times on Windows are dramatically slower than on the unix systems. This might be because the 100K BLOBs are all stored in a single directory and Windows is inefficient at searching directories with large numbers of files. The Windows file access times might be improved if the BLOBs were stored in a hierarchy of directories, rather than dumping them all into a single big directory. <h2>Key Points</h2> <ol> |