Reply to thread

Message

<blockquote data-quote="RonD" data-source="post: 1198056" data-attributes="member: 117536">My guess is reformatting gave windows a chance to detect/remap bad blocks to avoid using warn-out parts of the thumb drive. The thumb drive's internal flash controller also has logic that tries to detect/remap bad blocks. From a personal point of view, I view Thumb drives as a &quot;2016 floppy drive&quot; with N*GB data storage. Good for moving data around, but not really a high performance &quot;disk drive&quot;.At one time I experimented using thumb drives for time shifting with 2 or 3 thumb drives I had on my desk. One worked ok for the 1 afternoon of testing I did. The other 2 did not work well. They would start ok but every few minutes there would be on-screen glitches with lots of dropped frames. Played with windows file explorer to watch the files in the time shift folder, and Resource Monitor (DIsk) to see what windows showed for disk activity.The every few minutes &quot;glitch&quot; seemed to happen when TV Server switched to a new time shift file every 256-MB. Resource Monitor also showed a large spike in queue depth (number of rd/wr commands waiting for the drive). I guess when the tv server reach the end of each time shift file, windows and the thumb drive needed to fully flush/commit all write data to the drive, open/start writing the next time shift file and triggered lots of erase/write activity in the thumb drive that took extra time to complete. Went back to using an internal HDD for time shifting.</blockquote>

[QUOTE="RonD, post: 1198056, member: 117536"] My guess is reformatting gave windows a chance to detect/remap bad blocks to avoid using warn-out parts of the thumb drive. The thumb drive's internal flash controller also has logic that tries to detect/remap bad blocks. From a personal point of view, I view Thumb drives as a "2016 floppy drive" with N*GB data storage. Good for moving data around, but not really a high performance "disk drive". At one time I experimented using thumb drives for time shifting with 2 or 3 thumb drives I had on my desk. One worked ok for the 1 afternoon of testing I did. The other 2 did not work well. They would start ok but every few minutes there would be on-screen glitches with lots of dropped frames. Played with windows file explorer to watch the files in the time shift folder, and Resource Monitor (DIsk) to see what windows showed for disk activity. The every few minutes "glitch" seemed to happen when TV Server switched to a new time shift file every 256-MB. Resource Monitor also showed a large spike in queue depth (number of rd/wr commands waiting for the drive). I guess when the tv server reach the end of each time shift file, windows and the thumb drive needed to fully flush/commit all write data to the drive, open/start writing the next time shift file and triggered lots of erase/write activity in the thumb drive that took extra time to complete. Went back to using an internal HDD for time shifting. [/QUOTE]

Verification