all removable storage tests should run multiple iterations

Bug #1149213 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Medium
Jeff Lane 

Bug Description

The actual speed of transfer can vary greatly when running these tests against removable media. It all depends on what the kernel and CPU are doing at the time the test happens. You could see speed variances that are double or triple or more of the lowest speed.

For example, you could run removable_storage_test against a USB3.0 stick and get a very low 2MB/s, re-run and get 9MB's, re-run and get 6.8MB/s, re-run and get 5MB/s and so forth.

To combat this variance, I originally coded the test to allow for custom file sizes, multiple iterations and multiple files. All the removable storage tests (USB and MMC, Firewire and eSATA) should take advantage of this.

I would suggest as a starting point:

15 iterations of 100 1MB files...

or 15 iterations of 1 100MB file

or something else that will help really test the port.

Related branches

Jeff Lane  (bladernr)
Changed in checkbox:
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → Jeff Lane (bladernr)
status: In Progress → Fix Committed
Changed in checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.