Flashbench-results

flashbench-results@lists.linaro.org

174 discussions

by Richard Genoud

Hi Arnd, As you asked for flashbench results, here's some: Transcend µSDcard 2GB : flashbench -a /dev/mmcblk1 align 536870912 pre 3.24ms on 3.8ms post 2.67ms diff 845µs align 268435456 pre 3.05ms on 3.6ms post 2.53ms diff 814µs align 134217728 pre 3.11ms on 3.65ms post 2.56ms diff 814µs align 67108864 pre 3.07ms on 3.65ms post 2.52ms diff 854µs align 33554432 pre 3.08ms on 3.63ms post 2.49ms diff 851µs align 16777216 pre 3.09ms on 3.59ms post 2.58ms diff 756µs align 8388608 pre 3.25ms on 3.82ms post 2.68ms diff 850µs align 4194304 pre 2.93ms on 3.5ms post 2.52ms diff 772µs align 2097152 pre 2.96ms on 3.51ms post 2.49ms diff 788µs align 1048576 pre 2.45ms on 2.5ms post 2.47ms diff 37.6µs align 524288 pre 2.46ms on 2.47ms post 2.5ms diff -7440ns align 262144 pre 2.45ms on 2.47ms post 2.51ms diff -13815n align 131072 pre 2.45ms on 2.47ms post 2.49ms diff 2.15µs align 65536 pre 2.45ms on 2.47ms post 2.49ms diff -1188ns align 32768 pre 2.45ms on 2.46ms post 2.5ms diff -15476n Seems to be a 2MiB eraseblock Kingston µSD-HC card 4GB: flashbench -a /dev/mmcblk1 align 1073741824 pre 1.76ms on 2.09ms post 1.86ms diff 280µs align 536870912 pre 1.75ms on 2.09ms post 1.88ms diff 274µs align 268435456 pre 1.76ms on 2.1ms post 1.88ms diff 279µs align 134217728 pre 1.75ms on 2.1ms post 1.89ms diff 275µs align 67108864 pre 1.75ms on 2.11ms post 1.9ms diff 282µs align 33554432 pre 1.74ms on 2.09ms post 1.91ms diff 269µs align 16777216 pre 1.92ms on 2.26ms post 1.88ms diff 362µs align 8388608 pre 1.76ms on 2.1ms post 1.87ms diff 280µs align 4194304 pre 1.75ms on 2.09ms post 1.88ms diff 268µs align 2097152 pre 1.72ms on 1.91ms post 1.88ms diff 110µs align 1048576 pre 1.85ms on 2.02ms post 1.85ms diff 171µs align 524288 pre 1.72ms on 1.88ms post 1.85ms diff 98.5µs align 262144 pre 1.72ms on 1.91ms post 1.88ms diff 108µs align 131072 pre 1.73ms on 1.9ms post 1.87ms diff 96.3µs align 65536 pre 1.72ms on 1.9ms post 1.86ms diff 105µs align 32768 pre 1.72ms on 1.88ms post 1.85ms diff 89.5µs Seems to be a standard 4MiB eraseblock. Emmc 32GB: ./flashbench -a /dev/mmcblk0 align 8589934592 pre 467µs on 470µs post 470µs diff 1.25µs align 4294967296 pre 470µs on 469µs post 466µs diff 976ns align 2147483648 pre 472µs on 473µs post 476µs diff -1154ns align 1073741824 pre 479µs on 487µs post 483µs diff 5.83µs align 536870912 pre 474µs on 480µs post 481µs diff 2.9µs align 268435456 pre 490µs on 497µs post 486µs diff 8.85µs align 134217728 pre 485µs on 485µs post 486µs diff -145ns align 67108864 pre 491µs on 493µs post 480µs diff 7.05µs align 33554432 pre 495µs on 490µs post 495µs diff -4414ns align 16777216 pre 491µs on 496µs post 495µs diff 2.32µs align 8388608 pre 500µs on 504µs post 491µs diff 8.27µs align 4194304 pre 475µs on 492µs post 497µs diff 6.63µs align 2097152 pre 478µs on 477µs post 481µs diff -1896ns align 1048576 pre 481µs on 488µs post 488µs diff 3.58µs align 524288 pre 489µs on 489µs post 484µs diff 2.3µs align 262144 pre 487µs on 485µs post 479µs diff 1.92µs align 131072 pre 477µs on 477µs post 486µs diff -4437ns align 65536 pre 484µs on 487µs post 481µs diff 4.52µs align 32768 pre 485µs on 478µs post 484µs diff -6095ns I didn't see a pattern on this one. regards, Richard

11 years, 2 months

I am unsubscribing

by Martin Steigerwald

Hi! I am unsubscribing this mailing list due to what seems to excessive spam originating from China. In case you still want to reply to any of my posts, i.e. regarding my little shell script to automate analysis of cards and sticks a bit, using flashbench, then please CC me. This basically appears to be pretty quiet and unmaintained anyway. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

11 years, 7 months

SAMSUNG EVO 16GB SD Card

by Guilhermino Silva Correia

Name: SAMSUNG EVO UHS-1 HC-1 CL10 Size: 16GB ( 15.7GB, 15720251392 bytes ) Allocation Unit: 4MB Write Size: 32KB Page Size: 8KB FAT Location: - # open Aus linear: 28 # open Aus random: 28 Algorithm: random sector or page access ? Manuf ID: 0x1B OEMID: 0x534D NOTE: Another card with Manuf ID: 0x1D showed very inferior random write speeds compared to this one ( about 2x less ). I suspect it may be a fake, and curiously enough the good one was bought from Hong Kong on Ebay while this other was bought on a major store in my country.

11 years, 10 months

SanDisk Cruzer Blade 16GB results

by Gaby Schilders

Hi there, Here are my results for the SanDisk Cruzer Blade 16GB tests. The unit seems to behave a bit better than the smaller ones already in the list. The USB ID is identical to those of the smaller ones, however. At first, flashbench -a gave an uneven list of diff values. After reading that amount of writes can make a difference, I zeroed the (brand new) drive to all zeroes: dd if=/dev/zero of=/dev/sdx bs=4M. I then got the following: sudo flashbench -a /dev/sdf --blocksize=1024 align 4294967296 pre 748µs on 1.09ms post 756µs diff 335µs align 2147483648 pre 749µs on 1.16ms post 751µs diff 406µs align 1073741824 pre 748µs on 1.15ms post 751µs diff 402µs align 536870912 pre 746µs on 1.15ms post 750µs diff 401µs align 268435456 pre 752µs on 1.16ms post 752µs diff 408µs align 134217728 pre 738µs on 1.15ms post 756µs diff 406µs align 67108864 pre 749µs on 1.14ms post 749µs diff 395µs align 33554432 pre 753µs on 1.14ms post 752µs diff 392µs align 16777216 pre 746µs on 1.14ms post 754µs diff 394µs align 8388608 pre 745µs on 1.13ms post 747µs diff 388µs align 4194304 pre 744µs on 983µs post 747µs diff 237µs align 2097152 pre 752µs on 885µs post 744µs diff 137µs align 1048576 pre 753µs on 893µs post 753µs diff 140µs align 524288 pre 752µs on 880µs post 739µs diff 134µs align 262144 pre 750µs on 891µs post 757µs diff 137µs align 65536 pre 748µs on 888µs post 750µs diff 139µs align 32768 pre 749µs on 883µs post 745µs diff 137µs align 16384 pre 750µs on 890µs post 751µs diff 139µs align 8192 pre 745µs on 803µs post 748µs diff 56.8µs align 4096 pre 747µs on 804µs post 753µs diff 53.5µs align 2048 pre 746µs on 803µs post 745µs diff 57.3µs Leading to an assumption of erase size of 4M and page size of 8K. With a sequence of sudo flashbench -O --erasesize=$[4*1024*1024] --blocksize=$[8*1024] /dev/sdf --open-au-nr=X Where X increased linearly from 2 to 10 I determined the cutoff at AU=8 Because of: AU=2 4MiB 22M/s 2MiB 21.9M/s 1MiB 21.9M/s 512KiB 21.6M/s 256KiB 20.9M/s 128KiB 19.3M/s 64KiB 18.7M/s 32KiB 16.2M/s 16KiB 11.4M/s 8KiB 6.99M/s AU=7 4MiB 22M/s 2MiB 21.9M/s 1MiB 21.8M/s 512KiB 21.6M/s 256KiB 20.6M/s 128KiB 19.1M/s 64KiB 18.3M/s 32KiB 15.7M/s 16KiB 10.8M/s 8KiB 6.58M/s AU=8 4MiB 14.4M/s 2MiB 21.4M/s 1MiB 21.8M/s 512KiB 21.6M/s 256KiB 20.6M/s 128KiB 19.1M/s 64KiB 18.2M/s 32KiB 15.6M/s 16KiB 10.7M/s 8KiB 6.47M/s AU=9 4MiB 11.3M/s 2MiB 7M/s 1MiB 4.58M/s 512KiB 5.15M/s 256KiB 5.4M/s 128KiB 4.96M/s 64KiB 5.84M/s 32KiB 5.17M/s 16KiB 4.91M/s 8KiB 3.7M/s Random performance sucks at smaller sizes. Results nearly the same for AU=1 through 6 sudo flashbench -O --erasesize=$[4*1024*1024] --blocksize=$[8*1024] /dev/sdf --random --open-au-nr=6 [sudo] password for gaby: 4MiB 22.2M/s 2MiB 22M/s 1MiB 22M/s 512KiB 20M/s 256KiB 9.8M/s 128KiB 2.69M/s 64KiB 1.12M/s 32KiB 563K/s 16KiB 285K/s 8KiB 132K/s If there's anything else I can test/check, let me know? Regards, Gaby Schilders

11 years, 10 months

flashreport script

by Martin Steigerwald

I am not subscribed to linaro-dev, so please Cc me in case you drop flashbench-results mailinglist from receivers. Hi Arnd, hi everyone! For now quick and short. A simple script to automate common steps on reporting flash medium test results. It goes as far as read tests for erase block size and then suggests some open au tests together with a warning that these write to the device. I checked other flashbench-results posts as to what info would be interesting. Find it at: git://gitorious.org/flashbench/flashbench.git Example output is at: [Flashbench] Samsung Plus MB-SPAGFFP Class 10 SDHC 16GB Sat Dec 1 16:02:18 UTC 2012 http://lists.linaro.org/pipermail/flashbench-results/2012-December/000346.h… Sorry that I occupied flashbench upstream name for project. I can look into renaming it to "flashbench-martin" or something like that. The script is in branch "flashreport". In branch "defaultblocksize" you find a currently untested patch for changing default block size to 1024. I can try to send patches as mails via git, but I´d have to look it up first, since I do this quite rarely. Up to then please use the repo urls :) Nice weekend, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

12 years, 2 months

Samsung Memory MB-MP64D 64GB EVO MicroSDXC UHS-I Grade Class 10 MicroSDXC

by Martin Steigerwald

Hello! Three runs of my flashreport script[1] which uses flashbench as well as the open au benchmarks it suggested but additionally with report preferred erase block size as well. It seems pretty clear to me from the factory partitioning and the benchmark results that the device prefers an erase block size of large 16 MiB. But even with the reported default erase block size it seems to work quite well. Do you agree with this interpretation? I am not sure about the open au numbers as benchmark results do not vary much. It appears to me that it seems to slightly prefer lower open au numbers like 3 or 5 seem to be slightly preferable. For the intended use in Sandisk e260v1 with Rockbox open au numbers would not matter anyway as they are only setable with F2FS I think. The card indeed does work in it, reformatted to FAT32 (from ExFAT) and with partition type 0xc. I re-used the manufacturer partitioning. The included SD adapter from Samsung seems to have contact issues with SD card slot in ThinkPad T520. An Intenso I already had here one has no such issues. Except from kern.log: Aug 31 10:37:04 merkaba kernel: [215894.957529] mmc0: card 0001 removed Aug 31 10:37:06 merkaba kernel: [215896.457997] mmc0: new high speed SDXC card at address 0001 Aug 31 10:37:06 merkaba kernel: [215896.458528] mmcblk0: mmc0:0001 00000 58.5 GiB Aug 31 10:37:06 merkaba kernel: [215896.460570] mmc0: Got data interrupt 0x00200000 even though no data operation was in progress. Aug 31 10:37:06 merkaba kernel: [215896.460717] mmcblk0: error -110 sending status command, retrying Aug 31 10:37:06 merkaba kernel: [215896.460768] mmcblk0: error -110 sending status command, retrying Aug 31 10:37:06 merkaba kernel: [215896.460820] mmcblk0: error -110 sending status command, aborting Aug 31 10:37:06 merkaba kernel: [215896.460833] blk_update_request: 8 callbacks suppressed Aug 31 10:37:06 merkaba kernel: [215896.460837] end_request: I/O error, dev mmcblk0, sector 0 Aug 31 10:37:06 merkaba kernel: [215896.460842] quiet_error: 8 callbacks suppressed Aug 31 10:37:06 merkaba kernel: [215896.460846] Buffer I/O error on device mmcblk0, logical block 0 Aug 31 10:37:06 merkaba kernel: [215896.470999] mmc0: Controller never released inhibit bit(s). Aug 31 10:37:06 merkaba kernel: [215896.471207] mmcblk0: error -5 sending status command, retrying Aug 31 10:37:06 merkaba kernel: [215896.471272] mmcblk0: error -110 sending status command, retrying Aug 31 10:37:06 merkaba kernel: [215896.471324] mmcblk0: error -110 sending status command, aborting Aug 31 10:37:06 merkaba kernel: [215896.471337] end_request: I/O error, dev mmcblk0, sector 0 Aug 31 10:37:06 merkaba kernel: [215896.471343] Buffer I/O error on device mmcblk0, logical block 0 Aug 31 10:37:06 merkaba kernel: [215896.481525] mmc0: Controller never released inhibit bit(s). Aug 31 10:37:06 merkaba kernel: [215896.481678] mmcblk0: error -5 sending status command, retrying Aug 31 10:37:06 merkaba kernel: [215896.481742] mmcblk0: error -110 sending status command, retrying Aug 31 10:37:06 merkaba kernel: [215896.481796] mmcblk0: error -110 sending status command, aborting Aug 31 10:37:06 merkaba kernel: [215896.481809] end_request: I/O error, dev mmcblk0, sector 0 If I really insert it slowly and press it till the arrester it seems to work, but I rather prefer the Intenso adapter for now. Benchmark results follow: ===== Benchmarks in ThinkPad T520 internal SD card reader ===== merkaba:~> lspci -nn | grep MMC 0d:00.0 System peripheral [0880]: Ricoh Co Ltd MMC/SD Host Controller [1180:e822] (rev 08) merkaba:~> tail -fn0 /var/log/kern.log Aug 31 10:34:58 merkaba kernel: [215768.587240] mmc0: card 0001 removed Aug 31 10:35:50 merkaba kernel: [215820.887063] mmc0: new high speed SDXC card at address 0001 Aug 31 10:35:50 merkaba kernel: [215820.887507] mmcblk0: mmc0:0001 00000 58.5 GiB Aug 31 10:35:50 merkaba kernel: [215820.888892] mmcblk0: p1 Device has 62881005568 bytes: martin@merkaba:~> factor 62881005568 62881005568: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 937 === First run of flashreport script === martin@merkaba:~/[…]/flashbench> ./flashreport /dev/mmcblk0 ===> MMC card detected with erase block size of 524288 bytes <=== ==> find /sys/block/mmcblk0/device/ -maxdepth 1 -type f | xargs head <== ==> /sys/block/mmcblk0/device/cid <== 1b534d303030303010f216606c00e300 ==> /sys/block/mmcblk0/device/csd <== 400e00325b590001d47f7f800a404000 ==> /sys/block/mmcblk0/device/scr <== 02c5800300000000 ==> /sys/block/mmcblk0/device/date <== 03/2014 ==> /sys/block/mmcblk0/device/name <== 00000 ==> /sys/block/mmcblk0/device/type <== SD ==> /sys/block/mmcblk0/device/preferred_erase_size <== 16777216 ==> /sys/block/mmcblk0/device/fwrev <== 0x0 ==> /sys/block/mmcblk0/device/hwrev <== 0x1 ==> /sys/block/mmcblk0/device/oemid <== 0x534d ==> /sys/block/mmcblk0/device/manfid <== 0x00001b ==> /sys/block/mmcblk0/device/serial <== 0xf216606c ==> /sys/block/mmcblk0/device/uevent <== DRIVER=mmcblk MMC_TYPE=SD MMC_NAME=00000 MODALIAS=mmc:block ==> /sys/block/mmcblk0/device/erase_size <== 512 ==> fdisk -lu <== [sudo] password for martin: Disk /dev/mmcblk0: 58.6 GiB, 62881005568 bytes, 122814464 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 32768 122814463 122781696 58.6G 7 HPFS/NTFS/exFAT ==> sfdisk -d <== # partition table of /dev/mmcblk0 unit: sectors /dev/mmcblk0p1 : start= 32768, size=122781696, Id= 7 /dev/mmcblk0p2 : start= 0, size= 0, Id= 0 /dev/mmcblk0p3 : start= 0, size= 0, Id= 0 /dev/mmcblk0p4 : start= 0, size= 0, Id= 0 ===> Partition details <=== ==> sudo file -sk /dev/mmcblk0 <== /dev/mmcblk0: DOS/MBR boot sector; partition 1 : ID=0x7, start-CHS (0x2,10,9), end-CHS (0x3ff,254,63), startsector 32768, 122781696 sectors, extended partition table (last)\011 ==> sudo file -sk /dev/mmcblk0p1 <== /dev/mmcblk0p1: DOS/MBR boot sector ==> head -c20M | hexdump -C<== 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a |................| 000001c0 09 02 07 fe ff ff 00 80 00 00 00 80 51 07 00 00 |............Q...| 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01000000 eb 76 90 45 58 46 41 54 20 20 20 00 00 00 00 00 |.v.EXFAT .....| 01000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01000040 00 80 00 00 00 00 00 00 00 80 51 07 00 00 00 00 |..........Q.....| 01000050 00 40 00 00 00 40 00 00 00 80 00 00 00 51 07 00 |.@...@.......Q..| 01000060 04 00 00 00 00 00 00 00 00 01 00 00 09 08 01 80 |................| 01000070 00 00 00 00 00 00 00 00 f4 f4 f4 f4 f4 f4 f4 f4 |................| 01000080 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 |................| * 010001f0 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 55 aa |..............U.| 01000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010003f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01000400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010005f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01000600 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010007f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01000800 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010009f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01000a00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01000bf0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01000c00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01000df0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01000e00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01000ff0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01001000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010011f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01001200 46 7e 0c 0a 99 33 21 40 90 c8 fa 6d 38 9c 4b a2 |F~...3!@...m8.K.| 01001210 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01001600 d3 f8 4a 22 d3 f8 4a 22 d3 f8 4a 22 d3 f8 4a 22 |..J"..J"..J"..J"| * 01001800 eb 76 90 45 58 46 41 54 20 20 20 00 00 00 00 00 |.v.EXFAT .....| 01001810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01001840 00 80 00 00 00 00 00 00 00 80 51 07 00 00 00 00 |..........Q.....| 01001850 00 40 00 00 00 40 00 00 00 80 00 00 00 51 07 00 |.@...@.......Q..| 01001860 04 00 00 00 00 00 00 00 00 01 00 00 09 08 01 80 |................| 01001870 00 00 00 00 00 00 00 00 f4 f4 f4 f4 f4 f4 f4 f4 |................| 01001880 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 |................| * 010019f0 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 f4 55 aa |..............U.| 01001a00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01001bf0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01001c00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01001df0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01001e00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01001ff0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01002000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010021f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01002200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010023f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01002400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010025f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01002600 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010027f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01002800 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 010029f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 01002a00 46 7e 0c 0a 99 33 21 40 90 c8 fa 6d 38 9c 4b a2 |F~...3!@...m8.K.| 01002a10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01002e00 d3 f8 4a 22 d3 f8 4a 22 d3 f8 4a 22 d3 f8 4a 22 |..J"..J"..J"..J"| * 01003000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 01400000 ===> Trying to find erase block size by read tests <=== ==> sudo flashbench -a --count=100 --blocksize=1024 /dev/mmcblk0 <== align 17179869184 pre 439µs on 579µs post 277µs diff 221µs align 8589934592 pre 440µs on 580µs post 277µs diff 221µs align 4294967296 pre 437µs on 578µs post 274µs diff 223µs align 2147483648 pre 440µs on 580µs post 278µs diff 221µs align 1073741824 pre 440µs on 579µs post 277µs diff 221µs align 536870912 pre 440µs on 579µs post 277µs diff 221µs align 268435456 pre 439µs on 578µs post 277µs diff 221µs align 134217728 pre 446µs on 588µs post 286µs diff 222µs align 67108864 pre 444µs on 584µs post 282µs diff 221µs align 33554432 pre 414µs on 551µs post 275µs diff 207µs align 16777216 pre 422µs on 562µs post 287µs diff 207µs align 8388608 pre 280µs on 404µs post 281µs diff 124µs align 4194304 pre 284µs on 407µs post 279µs diff 126µs align 2097152 pre 291µs on 415µs post 291µs diff 124µs align 1048576 pre 295µs on 420µs post 291µs diff 127µs align 524288 pre 293µs on 417µs post 293µs diff 124µs align 262144 pre 287µs on 411µs post 282µs diff 127µs align 131072 pre 287µs on 411µs post 283µs diff 126µs align 65536 pre 287µs on 411µs post 291µs diff 122µs align 32768 pre 274µs on 397µs post 273µs diff 123µs align 16384 pre 274µs on 398µs post 274µs diff 124µs align 8192 pre 273µs on 273µs post 273µs diff 348ns align 4096 pre 281µs on 281µs post 281µs diff 136ns align 2048 pre 267µs on 267µs post 266µs diff 557ns (See README for an explaination on how to interpret the values.) Medium is a memory card which reports 524288 bytes as erase block size and 16777216 bytes as preferred erase size. ===> Suggestions for further benchmarking <=== Further tests can show the number of open erase blocks the medium can support. BEWARE: These tests write onto the device! Make a backup first! Further tests could look as follows: flashbench --open-au --open-au-nr=3 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] flashbench --open-au --open-au-nr=5 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] flashbench --open-au --open-au-nr=7 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] flashbench --open-au --open-au-nr=13 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] (Consult the README for further suggestions.) === Second run of flashreport script === martin@merkaba:~/…/flashbench> ./flashreport /dev/mmcblk0 ===> MMC card detected with erase block size of 524288 bytes <=== […] ===> Trying to find erase block size by read tests <=== ==> sudo flashbench -a --count=100 --blocksize=1024 /dev/mmcblk0 <== align 17179869184 pre 463µs on 602µs post 301µs diff 221µs align 8589934592 pre 462µs on 601µs post 299µs diff 221µs align 4294967296 pre 448µs on 588µs post 285µs diff 221µs align 2147483648 pre 467µs on 608µs post 304µs diff 223µs align 1073741824 pre 456µs on 595µs post 293µs diff 220µs align 536870912 pre 456µs on 596µs post 292µs diff 221µs align 268435456 pre 451µs on 593µs post 286µs diff 224µs align 134217728 pre 455µs on 594µs post 288µs diff 222µs align 67108864 pre 445µs on 585µs post 284µs diff 221µs align 33554432 pre 435µs on 573µs post 293µs diff 208µs align 16777216 pre 422µs on 560µs post 284µs diff 207µs align 8388608 pre 285µs on 409µs post 285µs diff 124µs align 4194304 pre 291µs on 416µs post 287µs diff 127µs align 2097152 pre 294µs on 417µs post 293µs diff 124µs align 1048576 pre 292µs on 416µs post 288µs diff 126µs align 524288 pre 287µs on 409µs post 285µs diff 124µs align 262144 pre 283µs on 407µs post 278µs diff 126µs align 131072 pre 285µs on 409µs post 280µs diff 126µs align 65536 pre 283µs on 407µs post 287µs diff 122µs align 32768 pre 289µs on 411µs post 288µs diff 123µs align 16384 pre 278µs on 402µs post 278µs diff 124µs align 8192 pre 282µs on 281µs post 281µs diff -523ns align 4096 pre 283µs on 283µs post 283µs diff 131ns align 2048 pre 286µs on 285µs post 285µs diff -817ns (See README for an explaination on how to interpret the values.) Medium is a memory card which reports 524288 bytes as erase block size and 16777216 bytes as preferred erase size. […] === Third run of flashreport script === martin@merkaba:~/…/flashbench> ./flashreport /dev/mmcblk0 […] ===> Trying to find erase block size by read tests <=== ==> sudo flashbench -a --count=100 --blocksize=1024 /dev/mmcblk0 <== align 17179869184 pre 457µs on 597µs post 295µs diff 221µs align 8589934592 pre 453µs on 593µs post 289µs diff 222µs align 4294967296 pre 463µs on 602µs post 299µs diff 221µs align 2147483648 pre 447µs on 586µs post 284µs diff 221µs align 1073741824 pre 450µs on 590µs post 286µs diff 222µs align 536870912 pre 451µs on 590µs post 286µs diff 221µs align 268435456 pre 446µs on 585µs post 283µs diff 221µs align 134217728 pre 449µs on 589µs post 285µs diff 222µs align 67108864 pre 453µs on 594µs post 291µs diff 222µs align 33554432 pre 420µs on 557µs post 280µs diff 206µs align 16777216 pre 423µs on 560µs post 284µs diff 207µs align 8388608 pre 284µs on 408µs post 283µs diff 124µs align 4194304 pre 291µs on 415µs post 286µs diff 127µs align 2097152 pre 286µs on 409µs post 285µs diff 124µs align 1048576 pre 290µs on 414µs post 286µs diff 126µs align 524288 pre 293µs on 419µs post 293µs diff 126µs align 262144 pre 287µs on 412µs post 283µs diff 127µs align 131072 pre 285µs on 408µs post 279µs diff 126µs align 65536 pre 301µs on 426µs post 305µs diff 123µs align 32768 pre 283µs on 408µs post 283µs diff 124µs align 16384 pre 279µs on 403µs post 278µs diff 124µs align 8192 pre 279µs on 279µs post 279µs diff 300ns align 4096 pre 280µs on 279µs post 279µs diff 133ns align 2048 pre 279µs on 279µs post 279µs diff 52ns (See README for an explaination on how to interpret the values.) Medium is a memory card which reports 524288 bytes as erase block size and 16777216 bytes as preferred erase size. […] Some open au write benchmarks. It seems to me: Either the Samsung rating of 48 MB/s is highly overrated or the cardreader is not UHS-1 capable. martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=3 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB 12.5M/s 256KiB 14M/s 128KiB 13.8M/s 64KiB 14.2M/s 32KiB 14.6M/s 16KiB 10.5M/s 8KiB 6.45M/s 4KiB 3.54M/s 2KiB 1.87M/s 1KiB 922K/s martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=5 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB 14M/s 256KiB 14.3M/s 128KiB 12.6M/s 64KiB 13.3M/s 32KiB 12.7M/s 16KiB 11.6M/s 8KiB 7.11M/s 4KiB 3.8M/s 2KiB 1.93M/s 1KiB 973K/s martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=7 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB 13.6M/s 256KiB 14M/s 128KiB 14.2M/s 64KiB 13.3M/s 32KiB 12.8M/s 16KiB 11.5M/s 8KiB 6.68M/s 4KiB 3.73M/s 2KiB 1.93M/s 1KiB 962K/s martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=13 --erasesize=524288 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 512KiB 13.5M/s 256KiB 14M/s 128KiB 13.9M/s 64KiB 12.9M/s 32KiB 12.4M/s 16KiB 10.7M/s 8KiB 6.79M/s 4KiB 3.76M/s 2KiB 1.86M/s 1KiB 957K/s martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=3 --erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 16MiB 14.1M/s 8MiB 13.6M/s 4MiB 13.5M/s 2MiB 13.6M/s 1MiB 13.4M/s 512KiB 13.3M/s 256KiB 13.1M/s 128KiB 12.9M/s 64KiB 12.9M/s 32KiB 13.1M/s 16KiB 10.4M/s 8KiB 6.37M/s 4KiB 3.6M/s 2KiB 1.83M/s 1KiB 948K/s martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=5 --erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 16MiB 13.8M/s 8MiB 13.6M/s 4MiB 13.5M/s 2MiB 13.7M/s 1MiB 13.5M/s 512KiB 13.3M/s 256KiB 13.4M/s 128KiB 13M/s 64KiB 12.7M/s 32KiB 12.2M/s 16KiB 9.88M/s 8KiB 6.14M/s 4KiB 3.54M/s 2KiB 1.76M/s 1KiB 897K/s martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=7 --erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 16MiB 13.7M/s 8MiB 13.6M/s 4MiB 13.6M/s 2MiB 13.4M/s 1MiB 13.4M/s 512KiB 13.1M/s 256KiB 13.3M/s 128KiB 13M/s 64KiB 12.8M/s 32KiB 12.2M/s 16KiB 9.91M/s 8KiB 6.18M/s 4KiB 3.54M/s 2KiB 1.76M/s 1KiB 914K/s martin@merkaba:~/[…]/flashbench> sudo flashbench --open-au --open-au-nr=13 --erasesize=16777216 --blocksize=1024 /dev/mmcblk0 --offset=$[24*1024*1024] 16MiB 13.9M/s 8MiB 13.6M/s 4MiB 13.8M/s 2MiB 13.4M/s 1MiB 13.5M/s 512KiB 13.2M/s 256KiB 12.8M/s 128KiB 12M/s 64KiB 11M/s 32KiB 9.37M/s 16KiB 6.45M/s 8KiB 3.07M/s 4KiB 1.6M/s 2KiB 797K/s 1KiB 408K/s ===== Benchmarks in digisol 2.0 Multi Card Reader 5.1 ===== Seems to be a Transcend reader: merkaba:~> lsusb | grep Transcend Bus 002 Device 007: ID 1307:0330 Transcend Information, Inc. 63-in-1 Multi-Card Reader/Writer merkaba:~> tail -fn0 /var/log/kern.log Aug 31 10:51:49 merkaba kernel: [216779.647323] usb 2-1.1: new high-speed USB device number 7 using ehci-pci Aug 31 10:51:49 merkaba kernel: [216779.930706] usb 2-1.1: New USB device found, idVendor=1307, idProduct=0330 Aug 31 10:51:49 merkaba kernel: [216779.930721] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 31 10:51:49 merkaba kernel: [216779.930728] usb 2-1.1: Product: Mass Storage Device Aug 31 10:51:49 merkaba kernel: [216779.930734] usb 2-1.1: Manufacturer: Generic Aug 31 10:51:49 merkaba kernel: [216779.930739] usb 2-1.1: SerialNumber: 00000000000006 Aug 31 10:51:49 merkaba kernel: [216779.931712] usb-storage 2-1.1:1.0: USB Mass Storage device detected Aug 31 10:51:49 merkaba kernel: [216779.931996] scsi host13: usb-storage 2-1.1:1.0 Aug 31 10:51:50 merkaba kernel: [216780.935185] scsi 13:0:0:0: Direct-Access Generic USB CF Reader 0.00 PQ: 0 ANSI: 2 Aug 31 10:51:50 merkaba kernel: [216780.935856] scsi 13:0:0:1: Direct-Access Generic USB SD Reader 0.00 PQ: 0 ANSI: 2 Aug 31 10:51:50 merkaba kernel: [216780.936529] scsi 13:0:0:2: Direct-Access Generic Mini SD Reader 0.00 PQ: 0 ANSI: 2 Aug 31 10:51:50 merkaba kernel: [216780.937054] scsi 13:0:0:3: Direct-Access Generic USB MS Reader 0.00 PQ: 0 ANSI: 2 Aug 31 10:51:50 merkaba kernel: [216780.937556] scsi 13:0:0:4: Direct-Access Generic USB SM Reader 0.00 PQ: 0 ANSI: 2 Aug 31 10:51:50 merkaba kernel: [216780.938602] sd 13:0:0:0: Attached scsi generic sg3 type 0 Aug 31 10:51:50 merkaba kernel: [216780.940382] sd 13:0:0:1: Attached scsi generic sg4 type 0 Aug 31 10:51:50 merkaba kernel: [216780.942365] sd 13:0:0:2: Attached scsi generic sg5 type 0 Aug 31 10:51:50 merkaba kernel: [216780.945763] sd 13:0:0:0: [sdc] Attached SCSI removable disk Aug 31 10:51:50 merkaba kernel: [216780.947310] sd 13:0:0:3: Attached scsi generic sg6 type 0 Aug 31 10:51:50 merkaba kernel: [216780.948245] sd 13:0:0:4: Attached scsi generic sg7 type 0 Aug 31 10:51:50 merkaba kernel: [216780.948512] sd 13:0:0:2: [sde] Attached SCSI removable disk Aug 31 10:51:50 merkaba kernel: [216780.949139] sd 13:0:0:1: [sdd] Attached SCSI removable disk Aug 31 10:51:50 merkaba kernel: [216780.952637] sd 13:0:0:3: [sdf] Attached SCSI removable disk Aug 31 10:51:50 merkaba kernel: [216780.954517] sd 13:0:0:4: [sdg] Attached SCSI removable disk merkaba:~> tail -fn0 /var/log/kern.log Aug 31 10:54:39 merkaba kernel: [216949.712566] sd 14:0:0:1: [sdd] 2048 512-byte logical blocks: (1.04 MB/1.00 MiB) Aug 31 10:54:39 merkaba kernel: [216949.717781] sdd: sdd1 Aug 31 10:54:39 merkaba kernel: [216949.717841] sdd: p1 start 32768 is beyond EOD, enabling native capacity Aug 31 10:54:39 merkaba kernel: [216949.721094] sdd: sdd1 Aug 31 10:54:39 merkaba kernel: [216949.721129] sdd: p1 start 32768 is beyond EOD, truncated Lol, can´t read this SDXC card it seems. :) [1] git@gitorious.org:flashbench-martin21/flashbench.git Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

12 years, 2 months

Sandisk Extreme 16GB MicroSDHC - unclear results

by Marcel Partap

Salut, for housing a debian chroot in my android phone, I want to set up a 2.5G partition on this new micro sd card. For that, I want to figure out which parameters to give to mke2fs, as in > mkfs.ext4 -E stride=2,stripe-width=2048 -L debian_chroot /dev/sdb2 Now to figure out the internal erase block size, flashbench was recommended. But I can not quite make sense of my result.. > # fdisk.distrib -l /dev/sdb > > Disk /dev/sdb: 15.9 GB, 15931539456 bytes > 255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x000604f9 > > Device Boot Start End Blocks Id System > /dev/sdb1 2048 25890815 12944384 b W95 FAT32 > /dev/sdb2 25890816 31115263 2612224 83 Linux > # flashbench -va /dev/sdb --blocksize=1024 |(echo "align,pre [µs],on [µs],post [µs],diff [µs]" && sed -r 's/\w+ //g;s/\t/,/g;s/[0-9]+ns*/0/g;s/µs//g')|tee flashbench-16gb-sandisk-extreme-microsdhc-blocksize-1024.csv > # flashbench -va /dev/sdb --blocksize=$[3*1024] |(echo "align,pre [µs],on [µs],post [µs],diff [µs]" && sed -r 's/\w+ //g;s/\t/,/g;s/[0-9]+ns*/0/g;s/µs//g')|tee flashbench-16gb-sandisk-extreme-microsdhc-blocksize-$[3*1024].csv resulting CSV files attached.. I created a spreadsheet chart showing a drop.. does this mean the erasure block size is 128KB? That would give a stripe-width of 128KB/(2*4KB)=16? And I have not at all grokked the benefit/applicability of open-au/open-au-nr for practical purposes.. Any clarification greatly appreciated. #Regards!Marcel

12 years, 2 months

SanDisk Cruzer Fit 32 GB USB disk SDCZ33-032G-B35

by Andrew Bradford

andrew@boomboom:~/git/flashbench$ /sbin/fdisk -l /dev/sdc Disk /dev/sdc: 32.0 GB, 32015679488 bytes 255 heads, 63 sectors/track, 3892 cylinders, total 62530624 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 32 62530623 31265296 c W95 FAT32 (LBA) andrew@boomboom:~/git/flashbench$ factor 32015679488 32015679488: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 13 17 4421 andrew@boomboom:~/git/flashbench$ sudo ./flashbench -a /dev/sdc --count=100 --blocksize=2048 [sudo] password for andrew: align 8589934592 pre 1.05ms on 1.29ms post 1ms diff 264µs align 4294967296 pre 1.02ms on 1.41ms post 1.01ms diff 398µs align 2147483648 pre 1.07ms on 1.43ms post 1.04ms diff 372µs align 1073741824 pre 1.03ms on 1.41ms post 1.01ms diff 384µs align 536870912 pre 1.06ms on 1.4ms post 994µs diff 371µs align 268435456 pre 1.02ms on 1.4ms post 1.01ms diff 386µs align 134217728 pre 1.06ms on 1.39ms post 1.01ms diff 358µs align 67108864 pre 1.03ms on 1.39ms post 998µs diff 378µs align 33554432 pre 1.03ms on 1.4ms post 993µs diff 390µs align 16777216 pre 1.02ms on 1.38ms post 1.01ms diff 370µs align 8388608 pre 1.05ms on 1.38ms post 1.01ms diff 349µs align 4194304 pre 1.02ms on 1.24ms post 979µs diff 241µs align 2097152 pre 1.04ms on 1.06ms post 1.03ms diff 26.2µs align 1048576 pre 1.03ms on 1.03ms post 1.02ms diff -766ns align 524288 pre 974µs on 1ms post 993µs diff 19.9µs align 262144 pre 1.01ms on 1.01ms post 999µs diff 11µs align 131072 pre 994µs on 1.01ms post 992µs diff 13.5µs align 65536 pre 996µs on 1.01ms post 997µs diff 8.89µs align 32768 pre 991µs on 1ms post 1ms diff 4.32µs align 16384 pre 1ms on 1.06ms post 1.06ms diff 28.1µs align 8192 pre 996µs on 1ms post 997µs diff 3.83µs align 4096 pre 997µs on 987µs post 980µs diff -801ns 4 MiB erase blocks andrew@boomboom:~/git/flashbench$ sudo ./flashbench /dev/sdc --open-au --blocksize=$[8*1024] --erasesize=$[4*1024*1024] --open-au-nr=1 4MiB 21.8M/s 2MiB 21.6M/s 1MiB 21.6M/s 512KiB 21.4M/s 256KiB 20.5M/s 128KiB 18.8M/s 64KiB 17.2M/s 32KiB 15.9M/s 16KiB 10.7M/s 8KiB 6.41M/s andrew@boomboom:~/git/flashbench$ sudo ./flashbench /dev/sdc --open-au --blocksize=$[8*1024] --erasesize=$[4*1024*1024] --open-au-nr=2 4MiB 21.7M/s 2MiB 21.6M/s 1MiB 21.4M/s 512KiB 21.2M/s 256KiB 20.2M/s 128KiB 18.5M/s 64KiB 16.9M/s 32KiB 14.9M/s 16KiB 10.1M/s 8KiB 5.83M/s andrew@boomboom:~/git/flashbench$ sudo ./flashbench /dev/sdc --open-au --blocksize=$[8*1024] --erasesize=$[4*1024*1024] --open-au-nr=4 4MiB 21.7M/s 2MiB 21.6M/s 1MiB 21.5M/s 512KiB 21.2M/s 256KiB 20.2M/s 128KiB 18.5M/s 64KiB 17M/s 32KiB 15M/s 16KiB 9.97M/s 8KiB 5.85M/s andrew@boomboom:~/git/flashbench$ sudo ./flashbench /dev/sdc --open-au --blocksize=$[8*1024] --erasesize=$[4*1024*1024] --open-au-nr=6 4MiB 19.4M/s 2MiB 21.5M/s 1MiB 21.4M/s 512KiB 21.2M/s 256KiB 20.1M/s 128KiB 18.4M/s 64KiB 16.7M/s 32KiB 14.6M/s 16KiB 9.77M/s 8KiB 5.71M/s andrew@boomboom:~/git/flashbench$ sudo ./flashbench /dev/sdc --open-au --blocksize=$[8*1024] --erasesize=$[4*1024*1024] --open-au-nr=7 4MiB 12.7M/s 2MiB 8.04M/s 1MiB 4.52M/s andrew@boomboom:~/git/flashbench$ sudo ./flashbench /dev/sdc --open-au --blocksize=$[8*1024] --erasesize=$[4*1024*1024] --random --open-au-nr=1 4MiB 21.8M/s 2MiB 21.6M/s 1MiB 21.5M/s 512KiB 20.4M/s 256KiB 9.96M/s 128KiB 2.71M/s 64KiB 1.12M/s 32KiB 564K/s 16KiB 285K/s 8KiB 132K/s andrew@boomboom:~/git/flashbench$ sudo ./flashbench /dev/sdc --find-fat 4MiB 21.8M/s 21.8M/s 21.7M/s 21.8M/s 9.03M/s 5.15M/s 2MiB 5.78M/s 21.2M/s 21.7M/s 21.6M/s 21.6M/s 21.6M/s 1MiB 21.4M/s 21.5M/s 21.5M/s 21.5M/s 21.5M/s 21.4M/s 512KiB 21.2M/s 21.3M/s 21.3M/s 21.3M/s 21.4M/s 21.4M/s 256KiB 20.4M/s 20.4M/s 20.4M/s 20.5M/s 20.5M/s 20.4M/s 128KiB 18.7M/s 18.8M/s 18.8M/s 18.8M/s 18.9M/s 18.7M/s 64KiB 16.9M/s 17M/s 17M/s 16.9M/s 16.9M/s 16.9M/s 32KiB 15.6M/s 15.1M/s 15.2M/s 15.6M/s 15.5M/s 15.2M/s 16KiB 10.2M/s 10.3M/s 10.3M/s 10.2M/s 10.2M/s 10.1M/s

12 years, 5 months

Samsung Pro Series 16 GB SDHC MB-SGAGB

by Andrew Bradford

Another quite good Samsung card. root@localhost:~/flashbench# head /sys/block/mmcblk1/device/* 2>/dev/null | grep -v ^$ ==> /sys/block/mmcblk1/device/block <== ==> /sys/block/mmcblk1/device/cid <== 1b534d303030303010a46d02c100e127 ==> /sys/block/mmcblk1/device/csd <== 400e00325b590000773c7f800a40409b ==> /sys/block/mmcblk1/device/date <== 01/2014 ==> /sys/block/mmcblk1/device/driver <== ==> /sys/block/mmcblk1/device/erase_size <== 512 ==> /sys/block/mmcblk1/device/fwrev <== 0x0 ==> /sys/block/mmcblk1/device/hwrev <== 0x1 ==> /sys/block/mmcblk1/device/manfid <== 0x00001b ==> /sys/block/mmcblk1/device/name <== 00000 ==> /sys/block/mmcblk1/device/oemid <== 0x534d ==> /sys/block/mmcblk1/device/power <== ==> /sys/block/mmcblk1/device/preferred_erase_size <== 4194304 ==> /sys/block/mmcblk1/device/scr <== 02b5800200000000 ==> /sys/block/mmcblk1/device/serial <== 0xa46d02c1 ==> /sys/block/mmcblk1/device/subsystem <== ==> /sys/block/mmcblk1/device/type <== SD ==> /sys/block/mmcblk1/device/uevent <== DRIVER=mmcblk MMC_TYPE=SD MMC_NAME=00000 MODALIAS=mmc:block root@localhost:~/flashbench# fdisk -l /dev/mmcblk1 Disk /dev/mmcblk1: 16.0 GB, 16003891200 bytes 255 heads, 63 sectors/track, 1945 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/mmcblk1p1 1 1946 15624704 c W95 FAT32 (LBA) root@localhost:~/flashbench# factor 16003891200 16003891200: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 5 5 11 37 root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 -a --blocksize=1024 --count=100 align 4294967296 pre 350µs on 485µs post 350µs diff 135µs align 2147483648 pre 352µs on 486µs post 350µs diff 135µs align 1073741824 pre 354µs on 485µs post 348µs diff 135µs align 536870912 pre 351µs on 486µs post 349µs diff 136µs align 268435456 pre 353µs on 485µs post 353µs diff 132µs align 134217728 pre 352µs on 487µs post 350µs diff 136µs align 67108864 pre 351µs on 485µs post 352µs diff 133µs align 33554432 pre 351µs on 483µs post 349µs diff 133µs align 16777216 pre 350µs on 485µs post 349µs diff 136µs align 8388608 pre 347µs on 498µs post 361µs diff 144µs align 4194304 pre 377µs on 488µs post 363µs diff 118µs align 2097152 pre 378µs on 485µs post 360µs diff 116µs align 1048576 pre 352µs on 487µs post 361µs diff 130µs align 524288 pre 375µs on 487µs post 362µs diff 118µs align 262144 pre 378µs on 488µs post 363µs diff 117µs align 131072 pre 377µs on 476µs post 359µs diff 108µs align 65536 pre 376µs on 484µs post 360µs diff 117µs align 32768 pre 378µs on 489µs post 360µs diff 120µs align 16384 pre 350µs on 460µs post 351µs diff 110µs align 8192 pre 353µs on 356µs post 353µs diff 2.79µs align 4096 pre 358µs on 353µs post 353µs diff -2687ns align 2048 pre 358µs on 359µs post 358µs diff 771ns Might be 8 MiB erase blocks. root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --blocksize=$[16*1024] --erasesize=$[8*1024*1024] --open-au-nr=1 8MiB 13.6M/s 4MiB 13.6M/s 2MiB 13.6M/s 1MiB 13.5M/s 512KiB 13.5M/s 256KiB 13.2M/s 128KiB 12.6M/s 64KiB 11.5M/s 32KiB 9.83M/s 16KiB 6.63M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --blocksize=$[16*1024] --erasesize=$[8*1024*1024] --open-au-nr=2 8MiB 13.6M/s 4MiB 13.7M/s 2MiB 13.6M/s 1MiB 13.6M/s 512KiB 13.4M/s 256KiB 13.2M/s 128KiB 12.6M/s 64KiB 11.4M/s 32KiB 9.87M/s 16KiB 6.66M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --blocksize=$[16*1024] --erasesize=$[8*1024*1024] --open-au-nr=7 8MiB 13.7M/s 4MiB 13.7M/s 2MiB 13.7M/s 1MiB 13.6M/s 512KiB 13.5M/s 256KiB 13.3M/s 128KiB 12.6M/s 64KiB 11.5M/s 32KiB 9.92M/s 16KiB 6.69M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --blocksize=$[16*1024] --erasesize=$[8*1024*1024] --open-au-nr=20 8MiB 13.7M/s 4MiB 13.7M/s 2MiB 13.7M/s 1MiB 13.6M/s 512KiB 13.5M/s 256KiB 13.3M/s 128KiB 12.6M/s 64KiB 11.5M/s 32KiB 9.99M/s 16KiB 6.72M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --blocksize=$[16*1024] --erasesize=$[8*1024*1024] --random --open-au-nr=20 8MiB 13.7M/s 4MiB 13.7M/s 2MiB 13.7M/s 1MiB 13.6M/s 512KiB 13.5M/s 256KiB 13.3M/s 128KiB 12.6M/s 64KiB 11.5M/s 32KiB 9.96M/s 16KiB 4.15M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --find-fat 4MiB 13.3M/s 13.8M/s 13.7M/s 13.8M/s 13.6M/s 13.7M/s 2MiB 13.5M/s 13.6M/s 13.8M/s 13.8M/s 13.6M/s 13.8M/s 1MiB 13.7M/s 13.7M/s 13.7M/s 13.7M/s 13.6M/s 13.7M/s 512KiB 13.5M/s 13.5M/s 13.5M/s 13.6M/s 13.5M/s 13.6M/s 256KiB 13.3M/s 13.4M/s 13.1M/s 13.3M/s 13.3M/s 13.4M/s 128KiB 12.6M/s 12.6M/s 12.7M/s 12.7M/s 12.6M/s 12.7M/s 64KiB 11.5M/s 11.5M/s 11.5M/s 11.5M/s 11.5M/s 11.5M/s 32KiB 10M/s 9.92M/s 10.1M/s 9.93M/s 10M/s 10M/s 16KiB 6.74M/s 6.68M/s 6.76M/s 6.68M/s 6.73M/s 6.71M/s -Andrew

12 years, 5 months

Kingston 4GB microSDHC SDC4

by Andrew Bradford

I tested this card, but an older one, 2 years back: http://lists.linaro.org/pipermail/flashbench-results/2012-February/000252.h… This is a newer one and is different. root@localhost:~# head /sys/block/mmcblk1/device/* 2>/dev/null | grep -v ^$ ==> /sys/block/mmcblk1/device/block <== ==> /sys/block/mmcblk1/device/cid <== 02544d5341303447113533890900d371 ==> /sys/block/mmcblk1/device/csd <== 400e00325b5900001d177f800a40008d ==> /sys/block/mmcblk1/device/date <== 03/2013 ==> /sys/block/mmcblk1/device/driver <== ==> /sys/block/mmcblk1/device/erase_size <== 512 ==> /sys/block/mmcblk1/device/fwrev <== 0x1 ==> /sys/block/mmcblk1/device/hwrev <== 0x1 ==> /sys/block/mmcblk1/device/manfid <== 0x000002 ==> /sys/block/mmcblk1/device/name <== SA04G ==> /sys/block/mmcblk1/device/oemid <== 0x544d ==> /sys/block/mmcblk1/device/power <== ==> /sys/block/mmcblk1/device/preferred_erase_size <== 4194304 ==> /sys/block/mmcblk1/device/scr <== 0235800001000000 ==> /sys/block/mmcblk1/device/serial <== 0x35338909 ==> /sys/block/mmcblk1/device/subsystem <== ==> /sys/block/mmcblk1/device/type <== SD ==> /sys/block/mmcblk1/device/uevent <== DRIVER=mmcblk MMC_TYPE=SD MMC_NAME=SA04G MODALIAS=mmc:block root@localhost:~/flashbench# fdisk -l /dev/mmcblk1 Disk /dev/mmcblk1: 3904 MB, 3904897024 bytes 4 heads, 16 sectors/track, 119168 cylinders Units = cylinders of 64 * 512 = 32768 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mmcblk1 doesn't contain a valid partition table root@localhost:~/flashbench# factor 3904897024 3904897024: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 7 7 19 root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --open-au-nr=1 4MiB 6.45M/s 2MiB 5.19M/s 1MiB 5.19M/s 512KiB 5.1M/s 256KiB 5.15M/s 128KiB 5.14M/s 64KiB 5.1M/s 32KiB 4.94M/s 16KiB 3.71M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --open-au-nr=2 4MiB 3.88M/s 2MiB 5.19M/s 1MiB 5.12M/s 512KiB 5.06M/s 256KiB 4.99M/s 128KiB 4.77M/s 64KiB 4.64M/s 32KiB 4.53M/s 16KiB 3.38M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --open-au-nr=3 4MiB 4.47M/s 2MiB 5.19M/s 1MiB 5.17M/s 512KiB 5.12M/s 256KiB 4.96M/s 128KiB 4.77M/s 64KiB 4.65M/s 32KiB 4.49M/s 16KiB 3.36M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --open-au-nr=4 4MiB 6.06M/s 2MiB 4.49M/s 1MiB 2.82M/s 512KiB 1.25M/s 256KiB 607K/s 128KiB 302K/s ^C root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --random --open-au-nr=1 4MiB 3.07M/s 2MiB 2.13M/s 1MiB 3.24M/s 512KiB 1.44M/s 256KiB 1.76M/s 128KiB 1.91M/s 64KiB 1.36M/s 32KiB 1.18M/s 16KiB 1.2M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --random --open-au-nr=2 4MiB 3.03M/s 2MiB 2.58M/s 1MiB 3.26M/s 512KiB 1.44M/s 256KiB 1.75M/s 128KiB 1.9M/s 64KiB 1.36M/s 32KiB 1.17M/s 16KiB 1.18M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --random --open-au-nr=3 4MiB 3.03M/s 2MiB 2.78M/s 1MiB 3.25M/s 512KiB 1.44M/s 256KiB 1.76M/s 128KiB 1.9M/s 64KiB 1.36M/s 32KiB 1.18M/s 16KiB 1.19M/s root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --open-au --erasesize=$[4*1024*1024] --blocksize=$[16*1024] --random --open-au-nr=4 4MiB 3.33M/s 2MiB 2.92M/s 1MiB 2.48M/s 512KiB 1.2M/s 256KiB 595K/s 128KiB 298K/s 64KiB 150K/s ^C root@localhost:~/flashbench# ./flashbench /dev/mmcblk1 --find-fat --erasesize=$[4*1024*1024] 4MiB 865K/s 3.56M/s 3.01M/s 5.13M/s 5.14M/s 5.12M/s 2MiB 4.3M/s 4.88M/s 5.11M/s 5.16M/s 5.11M/s 5.3M/s 1MiB 3.99M/s 4.9M/s 5.23M/s 5.18M/s 5.17M/s 5.15M/s 512KiB 3.88M/s 4.81M/s 5.15M/s 5.16M/s 5.16M/s 5.15M/s 256KiB 4.35M/s 4.38M/s 5.17M/s 5.18M/s 5.17M/s 5.16M/s 128KiB 3.78M/s 4.8M/s 5.13M/s 5.12M/s 5.15M/s 5.14M/s 64KiB 4.27M/s 4.74M/s 5.08M/s 5.03M/s 5.08M/s 5.07M/s 32KiB 3.62M/s 4.29M/s 4.97M/s 4.96M/s 4.96M/s 4.95M/s 16KiB 3.01M/s 3.31M/s 3.74M/s 4.29M/s 4.3M/s 4.29M/s

12 years, 6 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Flashbench-results