Benchmark Option

Say in this option.
User will select available drives letters that they want to sample. Each will require about 10GB of empty space. (maybe the size is an option, eg: 1/5/10GB)
User will select 1 of the total selected drives as a parity drive.
Then FR will generate 10GB or random for the 1st drive, log the timing.
After it finish, then read the data off the 1st drive read it to null and time it. So now we have read/write speed for 1st drive.
repeat it to all the selected drive(including the parity drive).
At this point, all the drives now would have a sample of read/write speed to show.
Then delete the random data written on the parity drive and proceed to benchmarking RAID option.
The system then go through all the mention, em, a bit of small algorithm, and adjust one option at a time, each creating parity and log the timing.
The system pick a few of the best timing available to show user and present with the option.(or maybe a feature to save those options as prefer option to use later?)
Upon completion of this benchmark mode, all the files created during this process get delete.

I mean, all the function is already there. This should be relatively easy as there is nothing new being invented. TrueCrypt has benchmark also, doing similar thing, so why not? This way, not only user will get the best performance they can get, but also reduce the likelihood of users making poor configuration choices on a large data later on, which not only lead to poor performance but also unnecessary questions on the forum. Perhaps if the data(log) is being collected in a useful manner
, maybe user can volunteer to upload the said log/stat file that can help other comparing hardware and performance. Something like raid creation timing, harddrive model(but no serial number) read/write time, CPU & controllers make/models, memory size and maybe controller drivers version; those should be in the log as well. I think those are useful information.

Yeah, I have been pondering on that too and indeed all the functions are there to do this.
Benchmarking the Checkum, RAID engine, Disk I/O (Read/Write), or their combination through the whole RAID setup should be possible.

Log it on bug.flexraid.com so that we can better track it.