Choose a card:
Performance Stats
0
Cards tested
Average Sequential Read SpeedThe average speed at which the card was able to read data in a sequential fashion. Cards were tested by attempting to read as much data as possible, in a linear fashion starting at the beginning of the card, over a 30-second period. Cards were tested using a USB 3.0-enabled card reader.
Average Sequential Write SpeedThe average speed at which the card was able to write data in a sequential fashion. Cards were tested by attempting to write as much data as possible, in a linear fashion starting at the beginning of the card, over a 30-second period. Cards were tested using a USB 3.0-enabled card reader.
Average Random Read SpeedThe average speed at which the card was able to read data from the card in a random fashion. Cards were tested by attempting to perform as many 4KB read operations as possible, from randomly selected 4KB-aligned locations across the entire card, over a 30-second period. Cards were tested using a USB 3.0-enabled card reader. It should be noted that (a) this method of random testing does not follow the SD specification's prescribed method for Application Performance Class testing, and (b) the card readers I use do not support command queueing, which is required for Application Performance Class 2 (if the card supports it). Therefore, if a result indicates that card does not meet the results of a given Application Performance Class, it should not be taken as an indication that the card does not qualify for that Application Performance Class.
Average Random Write SpeedThe average speed at which the card was able to write data to the card in a random fashion. Cards were tested by attempting to perform as many 4KB write operations as possible, from randomly selected 4KB-aligned locations across the entire card, over a 30-second period. Cards were tested using a USB 3.0-enabled card reader. It should be noted that (a) this method of random testing does not follow the SD specification's prescribed method for Application Performance Class testing, and (b) the card readers I use do not support command queueing, which is required for Application Performance Class 2 (if the card supports it). Therefore, if a result indicates that a card does not meet the requirements of a given Application Performance Class, it should not be taken as an indication that the card does not qualify for that Application Performance Class.
= Below 50th percentile = 50th to 75th percentile = Above 75th percentile
Endurance Stats
0
Cards currently in testing
0
Cards completed testing
Average Rounds Completed
Average Time in Testing
Time to First FailureThe number of read/write cycles a card was able to complete before either (a) the first error that prevented the data from being read back, or (b) the first instance of a data mismatch (excluding instances where device mangling was confirmed). This does not include any cards that have not yet experienced their first error, but does include any cards that failed completely before experiencing their first error. While well-made cards (especially industrial-grade cards) tend to experience their first error later, I think that at least some of these errors may be due to issues with the card readers or the USB stack — therefore, I think that the "Time to 0.1% Failure" metric is a better indicator of a card's reliability.
0
Cards experienced first failure
Average Time to First Failure
Time to 0.1% FailureThe number of read/write cycles a card was able to complete before 0.1% of the sectors on the card were flagged as "bad". Sectors are flagged as "bad" if (a) an error occurs that prevents the data from being read back, or (b) if the data read back does not match the data originally written (and is not a device mangling error). This does not include any cards that have not yet reached the 0.1% failure threshold, but does include any cards that failed completely before reaching this threshold. This threshold was arbitrarily chosen, but is intended to reflect the point where a user would be likely notice that something was wrong with the card.
0
Cards reached 0.1% failure
Average Time to 0.1% Failure
Time to 1% FailureThe number of read/write cycles a card was able to complete before 1% of the sectors on the card were flagged as "bad". Sectors are flagged as "bad" if (a) an error occurs that prevents the data from being read back, or (b) if the data read back does not match the data originally written (and is not a device mangling error). This does not include any cards that have not yet reached the 1% failure threshold, but does include any cards that failed completely before reaching this threshold.
0
Cards reached 1% failure
Average Time to 1% Failure
Time to 10% FailureThe number of read/write cycles a card was able to complete before 10% of the sectors on the card were flagged as "bad". Sectors are flagged as "bad" if (a) an error occurs that prevents the data from being read back, or (b) if the data read back does not match the data originally written (and is not a device mangling error). This does not include any cards that have not yet reached the 10% failure threshold, but does include any cards that failed completely before reaching this threshold.
0
Cards reached 10% failure
Average Time to 10% Failure
Time to 25% FailureThe number of read/write cycles a card was able to complete before 25% of the sectors on the card were flagged as "bad". Sectors are flagged as "bad" if (a) an error occurs that prevents the data from being read back, or (b) if the data read back does not match the data originally written (and is not a device mangling error). This does not include any cards that have not yet reached the 25% failure threshold, but does include any cards that failed completely before reaching this threshold.
0
Cards reached 25% failure
Average time to 25% failure
Time to 50% failureThe number of read/write cycles a card was able to complete before 50% of the sectors on the card were flagged as "bad". Sectors are flagged as "bad" if (a) an error occurs that prevents the data from being read back, or (b) if the data read back does not match the data originally written (and is not a device mangling error). This does not include any cards that have not yet reached the 50% failure threshold, but does include any cards that failed completely before reaching this threshold.
0
Cards reached 50% failure
Average Time to 50% Failure
= Below 50th percentile = 50th to 75th percentile = Above 75th percentile
Whoops! Something went wrong while loading the data. Please try again later or try a different card.