Nice, you're on the right track.

Yeah it will indeed take a long time (especially if you have a MicroSD card larger than mine, e.g. 16GB or so). The way I understand it, the program tries to "write" data first to the card and does a "write" benchmark. And then you'd run a "read" benchmark where the program tries to "read" the data that was initially written. And then it will post the results to you.

Based on my experience in Post #1, running the benchmarking test in a Microsoft-based OS gave me higher numbers compared to F3 (Linux-based) when it comes to "read" speed. No matter what I did, F3 always gave me an average of 4 Mb/s "read" speed (although "write" speed seemed okay).

EDIT: I didn't notice you ran the command on /home/user...you are benchmarking the speed of the eMMC? (32GB, particularly the "Home" partition)?

EDIT 02: Hi Friend, saw your edit (posting the results). You may want to try using another tool, like the Windows-based tool so you can compare just like what I did. I got slower benchmarking results in the Linux-based program compared to Microsoft-based program.

EDIT 03: Your read speed is fast.

EDIT 04: Yes, it will indeed fill up the storage that you tried the benchmarking on. That's the intention of these tools as mentioned by the author of the program:

1. "Write" will place files to fill up the storage device and at the same time, will measure how fast it can "write" files to the storage.
2. "Read" will read the files that were initially "written" and will measure how fast it can "read" those files.

You can safely delete the new files that were "written" or "created" by the program after you finished your benchmarking, by the way. It's easy to identify those files that you need to delete; they are all in 1GB increments. The files are named:

...and so on.