[Flashbench] Corsair Voyager 3.0 16GB
arnd at arndb.de
Mon Jun 6 14:27:15 UTC 2011
On Monday 06 June 2011, Michael Monnerie wrote:
> As test #18 was running 9 minutes, but test #19 1h17m, I guess 18 would
> be the solution, right?
Yes, exactly. Thanks for the data, I'll add it to the wiki.
> Anything else to consider? What would be a good
> partition starting point? Is that stick FAT optimized?
I would start every partition at a multiple of 8 MB.
You can check if the FAT area is doing something special using
flashbench --findfat --fat-nr=5 --erasesize=$[8 * 1024*1024] --random --blocksize=512
I don't expect anything special to show up there, because the
stick can already handle random writes anywhere.
Using FAT32 is probably best because it uses 32 KB clusters if you tell
it to do that. Other file systems should be fine as well, they won't
suffer from lack of open erase blocks, although the 32 KB clusters
will hurt a bit when writing small files, regardless of the file system
I hope we can get other file systems in Linux to support large clusters
More information about the Flashbench-results