3 ms·
pretty sure it was ntfs formatted, so it would have already been enabled. not only that, they actually have a custom partition that gets created and needs to be
by leeoniya 12y ago
pretty sure it was ntfs formatted, so it would have already been enabled. not only that, they actually have a custom partition that gets created and needs to be mounted for their stuff to work. it doesnt "just work", so there's more going on there.
- acqq 12y agoIf the write cache is on (as you claim it was!) you don't benchmark the times it takes for some write actually end on the medium, only the time be copied to the RAM, so the measurements you quote have no sense. They also mention on their page "when the light stops blinking it's over" which means exactly this: the software already consider everything copied, but the movement from the RAM to the device still goes on -- and that is not measured. Moreover, the OS can combine more writes to the same area to one to the device so you can actually observe less writes to the device. I still suspect that software to be a kind of snake oil.
- leeoniya 12y agointeresting. i think i still have a license left if you want to test it out, lemme know.
- acqq 12y agoEven without the license, I have already some time ago measured the overhead of copying a lot of small files with and without OS write cache. They cite 1 GB data with the average file size of 154 KB which gives around 6500 files to copy, all on FAT32 (see "How fast is SuperCharger?") The overhead of the write cache turned off for that number of files on the old stick I had (on FAT32) was around 2 minutes and that, of course, measuring "the blinking stops" in the "on" case.