Flashbench-results

flashbench-results@lists.linaro.org

626 discussions

Re: [Flashbench] USB Stick: Corsair Flash Voyager GT

by Arnd Bergmann

On Thursday 24 March 2011, Michael Monnerie wrote: > We could speak german, I guess? Yes, but I'd prefer to keep the discussion on the mailing list if interesting results come up. > On Donnerstag, 24. März 2011 Arnd Bergmann wrote: > > > > Are these results reproducible? It's not at all clear to me that the > > erase size is really 4 MB, it could also be 1 MB for instance, > > especially if your stick is from before 2010. You can rerun the > > command with --count=100 or more, or with larger block sizes to get > > a better feeling. > > # ./flashbench -a /dev/sde --blocksize=4096 --count=100 > sched_setscheduler: Operation not permitted > align 536870912 pre 703µs on 798µs post 666µs diff 114µs > align 268435456 pre 700µs on 753µs post 681µs diff 62.8µs > align 134217728 pre 786µs on 783µs post 645µs diff 67.4µs > align 67108864 pre 723µs on 772µs post 675µs diff 73.3µs > align 33554432 pre 701µs on 762µs post 674µs diff 74.4µs > align 16777216 pre 701µs on 741µs post 685µs diff 48.3µs > align 8388608 pre 695µs on 749µs post 668µs diff 66.8µs > align 4194304 pre 706µs on 791µs post 671µs diff 102µs > align 2097152 pre 674µs on 707µs post 692µs diff 23.9µs > align 1048576 pre 683µs on 726µs post 701µs diff 34.3µs > align 524288 pre 671µs on 726µs post 717µs diff 32.3µs > align 262144 pre 698µs on 713µs post 687µs diff 20.7µs > align 131072 pre 682µs on 740µs post 704µs diff 46.9µs > align 65536 pre 687µs on 727µs post 697µs diff 35.1µs > align 32768 pre 712µs on 722µs post 692µs diff 19.9µs > align 16384 pre 667µs on 699µs post 674µs diff 27.9µs > align 8192 pre 702µs on 770µs post 686µs diff 75.8µs Ok, this is much clearer: I'm pretty sure that it's either 4 MB or 8 MB, based on this result. Note how all diff values below 4 MB are smaller than all diff values above 4 MB. Something strange is going at at 4 MB, so it's not clear whether it belongs to the upper or lower half. > # ./flashbench -a /dev/sde --blocksize=8192 --count=50 > sched_setscheduler: Operation not permitted > align 536870912 pre 879µs on 899µs post 858µs diff 30.9µs > align 268435456 pre 847µs on 906µs post 842µs diff 61.1µs > align 134217728 pre 996µs on 968µs post 836µs diff 52µs > align 67108864 pre 811µs on 839µs post 757µs diff 55µs > align 33554432 pre 871µs on 908µs post 847µs diff 48.7µs > align 16777216 pre 854µs on 914µs post 818µs diff 78µs > align 8388608 pre 851µs on 908µs post 850µs diff 58.2µs > align 4194304 pre 892µs on 880µs post 908µs diff -20511n > align 2097152 pre 828µs on 849µs post 885µs diff -7708ns > align 1048576 pre 874µs on 886µs post 862µs diff 17.9µs > align 524288 pre 852µs on 869µs post 915µs diff -15025n > align 262144 pre 844µs on 895µs post 940µs diff 2.73µs > align 131072 pre 848µs on 884µs post 907µs diff 6.1µs > align 65536 pre 837µs on 857µs post 840µs diff 18µs > align 32768 pre 831µs on 864µs post 861µs diff 17.7µs > align 16384 pre 855µs on 841µs post 826µs diff 201ns > > Could it be some linux cache is in the way? No, all I/O is done with O_DIRECT, which completely bypasses the page cache. In theory, there could be a cache on the stick, but that's rarely the case. The USB protocol adds some jitter here, and for some reason you cannot use real-time scheduling, which makes the results less accurate. > > Another helpful indication would be the output of 'fdisk -lu > > /dev/sde': It will show the start of the partition and the size of > > the drive, both should be a multiple of the erase block size. > > # fdisk -lu /dev/sde > > Disk /dev/sde: 16.2 GB, 16240345088 bytes > 255 heads, 63 sectors/track, 1974 cylinders, total 31719424 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: 0x925df597 Ok, 16240345088 bytes is 121 times 128 MiB, so it's certainly not using 4128 KiB blocks or some other strange unit. > Device Boot Start End Blocks Id System > /dev/sde1 63 31712309 15856123+ 7 HPFS/NTFS/exFAT > > I didn't use sde1 but sde for the tests, so it shouldn't have a meaning. > I'll change the partition to start at 2048 or whatever I find the erasesize to be. Be careful here. The original FAT layout is typically made specifically for this stick, so it's probably a good idea to make a backup of the first few blocks. > > Finally, a third way is to look at a gnuplot chart on the output of > > > > flashbench -s -o output.plot /dev/sde --scatter-order=10 > > --scatter-span=2 --blocksize=8192 gnuplot -p -e 'plot "output.plot"' > > > > On many drives, the boundaries between erase blocks show up as spikes > > in the chart. > > Phew, two lines, more or less, and spikes everwhere (see attached). Right, nothing to see here yet. It only shows the first 8 MB, so if the spike is every 8 MB, it won't show up here. Use --scatter-order=12 to show more. Also, the jitter from the USB protocol may hide some details, which might get better with a larger --count= value, but that would make the test run much longer. It's probably good enough to assume that the size is actually 8 MB or 4 MB, and keep going from there. > > Also, please post the USB ID and name output from 'lsusb' for > > reference. > > # lsusb -v > Bus 001 Device 005: ID 1b1c:1a90 Ok. > Now with 16 I got it slower, still no visible border: > > # ./flashbench -O --erasesize=$[4 * 1024 * 1024] --blocksize=$[64 * 1024] /dev/sde --open-au-nr=4 > sched_setscheduler: Operation not permitted > 4MiB 7.3M/s > 2MiB 11.2M/s > 1MiB 15.7M/s > 512KiB 19.2M/s > 256KiB 14.5M/s > 128KiB 12.8M/s > 64KiB 18.8M/s > # ./flashbench -O --erasesize=$[4 * 1024 * 1024] --blocksize=$[64 * 1024] /dev/sde --open-au-nr=16 > sched_setscheduler: Operation not permitted > 4MiB 9.77M/s > 2MiB 3.41M/s > 1MiB 7.38M/s > 512KiB 5.69M/s > ^C (took too long) If it takes too long, that's a good indication that something interesting is happening ;-) > Seems that stick wants to hide it's internals? Not completely unusual, but somewhat harder than most. I've committed some updates now that might help make the --open-au results a bit clearer, and faster. What I would recommend now is to update to the latest git version (just uploaded), and then try increasing numbers of --open-au-nr= with 4 MB erasesize, until you hit the cutoff. Try the same with --random, for the last fast one and the first slow one: ./flashbench -O --erasesize=$[4 * 1024 * 1024] /dev/sde --open-au-nr=5 ./flashbench -O --erasesize=$[4 * 1024 * 1024] /dev/sde --open-au-nr=6 ./flashbench -O --erasesize=$[4 * 1024 * 1024] /dev/sde --open-au-nr=7 ... ./flashbench -O --erasesize=$[4 * 1024 * 1024] /dev/sde --open-au-nr=N => N is the number of 4 MB blocks that can not be handled ./flashbench -O --erasesize=$[4 * 1024 * 1024] /dev/sde --open-au-nr=(N-1) --random ./flashbench -O --erasesize=$[4 * 1024 * 1024] /dev/sde --open-au-nr=N --random => Verify that the (N-1) --random case is still fast ./flashbench -O --erasesize=$[8 * 1024 * 1024] /dev/sde --open-au-nr=((N-1)/2) --random ./flashbench -O --erasesize=$[8 * 1024 * 1024] /dev/sde --open-au-nr=(N-1) --random ./flashbench -O --erasesize=$[8 * 1024 * 1024] /dev/sde --open-au-nr=(N-1) --random Arnd

14 years, 3 months

Re: [Flashbench] IPPBX For Distributor

by Alex

Dear Product Manager From google, we get to know that you focus on communication pruducts with high reputation.We are professional IP-PBX,GSM gateway manufacturer with high-quality and competitive price. MyPBX STD V4 is the newest version that supports PSTN,GSM,VoIP trunks with FXS / FXO / PRI / BRI (ISDN) ports. It is embedded hybrid IP-PBX which caters for the small businesses. Please feel free to contact me to get further information to open our cooperation relationship in 2011. Thanks&Best Regards Alex Yeastar Technology Co.,Ltd Web: www.yeastar.com MSN: hqy(a)yeastar.com Skype: Yeastar.hqy Tel: +86 592 5503309 Ext.8026 Add: 202,No.23 Wanghai Road, 2nd Software Park, Xiamen, China --------------------------------------------------------------------------------

14 years, 3 months

Better Air Price to Brazil +ACI- Sam BSI-THREE+ACI-

by Sam Peng / BSI-SZX

Dear Sir & Madam, Have a nice day ! This is Sam Peng from BSI (BEST SERVICES INT'L FREIGHT LTD) in China.we are as agent of Lufthansa Cargo / LH ; Lan Chile / LAN ; Bringer Air Cargo / E6 in China. We specialize in Air freight / Sea shipping to Brazil in China. It's my pleasure to send the the below air price for your reference. Shenzhen / Guangzhou / Dongguan ; China to San Paulo ; Brazil : 1) A/Freight : USD7.10/KG (more than 1000kgs) 2) Frequency : Fri 3) Airways : Emirates Skycargo Airlines / EK 4) Transit Time: 3~4days 5) Departure : from HongKong 6) Flight Route : HongKong--Dubai--San Paulo ***we can help you to pick up the goods from any city in China to Brazil*** Our Promise: -- Closely keep in touch with you & Supplier. -- Keep working with you in the same time as you to know all update information for your order in time. -- Combine the shipment from different supplier and make the combine packing list & commercial invoice to one set original document -- Assist you to check new supplier's company credit. -- Ensure Cargo to be loaded at the soonest. -- Ensure to provide best logsitics project to save your purchase cost. -- Keep update the cargo tracking information for you. Our Certifications: -- IATA: International Air Transport Association. -- NVOCC: Non Vessel Operating Common Carrier. -- WCA: Member of World Cargo Alliance. -- CATA: China Civil Air Transport Sales (Class A) Agency Services. I expect you to try our services for your air cargo to Brazil. I'm sure that our sincerely services can make you feel satisfied.Please don't hesitate to contact with me in any time. B. regards! Sam Peng Sales Dept BEST SERVICES INTERNATIONAL FREIGHT LTD Rm.B13-19, 10/F, Regalia Place, Jiabin Rd, Shenzhen, China. Tel : 86-755-25904212 Fax : 86-755-25901937 / 25901911 Cell Phone : +86-13760303532 E-mail : sales4.szx(a)bsigroup.cc MSN : sampeng8210(a)hotmail.com Skype : sampeng821007 Website: http://www.bestservices.com.cn IATA: 08-3 1624 CATA: ZN30165 FMC: 022856 NVOCC: MOC-NV03395 BSI Offices : Shenzhen, HongKong, Guangzhou, Shanghai, Ningbo, Xiamen, Dongguan, Zhongshan, Jiangmen. BSI representative offices : Qingdao, Dalian, Tianjin, Beijing, Lianyungang, Yantai, Fuzhou, Zhuhai, Shantou, Chongqing, Chengdu and others. All transactions are subject to the Company's Standard Trading Conditions ( copy is available upon request ), which in certain circumstances limit or exempt the Company's liability.

14 years, 3 months

USB Stick: Corsair Flash Voyager GT

by Michael Monnerie

I can't interpret the numbers for the AUs, can you help me? # ./flashbench -a /dev/sde --blocksize=1024 sched_setscheduler: Operation not permitted align 536870912 pre 745µs on 756µs post 696µs diff 36.2µs align 268435456 pre 698µs on 882µs post 670µs diff 198µs align 134217728 pre 722µs on 899µs post 715µs diff 180µs align 67108864 pre 720µs on 712µs post 669µs diff 17.1µs align 33554432 pre 750µs on 765µs post 639µs diff 70.1µs align 16777216 pre 727µs on 777µs post 684µs diff 71.8µs align 8388608 pre 691µs on 727µs post 646µs diff 58.3µs align 4194304 pre 689µs on 769µs post 675µs diff 87.3µs align 2097152 pre 697µs on 879µs post 715µs diff 173µs align 1048576 pre 716µs on 899µs post 789µs diff 147µs align 524288 pre 659µs on 775µs post 724µs diff 83.4µs align 262144 pre 657µs on 735µs post 685µs diff 63.6µs align 131072 pre 656µs on 706µs post 756µs diff -248ns align 65536 pre 655µs on 715µs post 650µs diff 62.3µs align 32768 pre 732µs on 792µs post 743µs diff 54.1µs align 16384 pre 685µs on 808µs post 767µs diff 82.6µs align 8192 pre 732µs on 764µs post 697µs diff 49.8µs align 4096 pre 661µs on 692µs post 681µs diff 20.7µs align 2048 pre 671µs on 657µs post 653µs diff -5465ns # ./flashbench -O --erasesize=$[4 * 1024 * 1024] --blocksize=$[256 * 1024] /dev/sde --open-au-nr=2 sched_setscheduler: Operation not permitted 4MiB 6.69M/s 2MiB 11.1M/s 1MiB 13.2M/s 512KiB 14.4M/s 256KiB 14.6M/s # ./flashbench -O --erasesize=$[4 * 1024 * 1024] --blocksize=$[256 * 1024] /dev/sde --open-au-nr=3 sched_setscheduler: Operation not permitted 4MiB 6.68M/s 2MiB 11.2M/s 1MiB 12.9M/s 512KiB 14.5M/s 256KiB 14.8M/s # ./flashbench -O --erasesize=$[4 * 1024 * 1024] --blocksize=$[256 * 1024] /dev/sde --open-au-nr=4 sched_setscheduler: Operation not permitted 4MiB 6.8M/s 2MiB 10.9M/s 1MiB 13M/s 512KiB 14.4M/s 256KiB 14.6M/s # ./flashbench -O --erasesize=$[4 * 1024 * 1024] --blocksize=$[256 * 1024] /dev/sde --open-au-nr=6 sched_setscheduler: Operation not permitted 4MiB 7.45M/s 2MiB 9.24M/s 1MiB 16.4M/s 512KiB 17.4M/s 256KiB 7.98M/s -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Internet Services: Protéger http://proteger.at [gesprochen: Prot-e-schee] Tel: +43 660 / 415 6531 // ****** Radiointerview zum Thema Spam ****** // http://www.it-podcast.at/archiv.html#podcast-100716 // // Haus zu verkaufen: http://zmi.at/langegg/

14 years, 3 months

You could find the competitive price mobile phone without B2B

by Picasa Web Albums

Dear Sir or Madam, Glad to hear that you're on the market for mobile phone. We, Wei Wan Technology are a professional manufacturer for mobile phone. Dual Sim card and Triple Sim card etc Please contact me if any questions. Sincerely hope to find a way to cooperate with your esteemed company! Thanks & best regards Juce E-mail: elink(a)vip.188.com Factory Address: 5/F, Building 21, ChenTian Industrial Park, BaoTian 2nd Road, Xixiang Town, Bao'anDistrict, Shenzhen, GuangDong Province, China

14 years, 3 months

Kingston microSD 2 GB (2010 model)

by Arnd Bergmann

$ head /sys/block/mmcblk0/device/{c*,scr,*rev,*id,serial,*size,name,date} ==> /sys/block/mmcblk0/device/cid <== 02544d534130324705200a985700a700 ==> /sys/block/mmcblk0/device/csd <== 002e00325b5aa3acffffff800a800000 ==> /sys/block/mmcblk0/device/scr <== 0225800001000000 ==> /sys/block/mmcblk0/device/fwrev <== 0x5 ==> /sys/block/mmcblk0/device/hwrev <== 0x0 ==> /sys/block/mmcblk0/device/cid <== 02544d534130324705200a985700a700 ==> /sys/block/mmcblk0/device/manfid <== 0x000002 ==> /sys/block/mmcblk0/device/oemid <== 0x544d ==> /sys/block/mmcblk0/device/serial <== 0x200a9857 ==> /sys/block/mmcblk0/device/erase_size <== 512 ==> /sys/block/mmcblk0/device/preferred_erase_size <== 4194304 ==> /sys/block/mmcblk0/device/name <== SA02G ==> /sys/block/mmcblk0/device/date <== 07/2010 $ sudo ./flashbench -a /dev/mmcblk0 --blocksize 1024 --count=50 [sudo] password for arnd: align 268435456 pre 1.45ms on 2.14ms post 1.19ms diff 819µs align 134217728 pre 1.77ms on 2.39ms post 1.26ms diff 874µs align 67108864 pre 1.78ms on 2.16ms post 1.19ms diff 677µs align 33554432 pre 1.77ms on 2.17ms post 1.21ms diff 680µs align 16777216 pre 1.58ms on 2.18ms post 1.21ms diff 788µs align 8388608 pre 1.26ms on 2.13ms post 1.21ms diff 900µs align 4194304 pre 1.3ms on 2.16ms post 1.21ms diff 911µs align 2097152 pre 1.5ms on 2.16ms post 1.18ms diff 822µs align 1048576 pre 1.21ms on 1.41ms post 1.24ms diff 186µs align 524288 pre 1.21ms on 1.27ms post 1.21ms diff 60.4µs align 262144 pre 1.21ms on 1.27ms post 1.21ms diff 59.3µs align 131072 pre 1.21ms on 1.27ms post 1.21ms diff 59.2µs align 65536 pre 1.21ms on 1.27ms post 1.21ms diff 59.2µs align 32768 pre 1.21ms on 1.27ms post 1.21ms diff 60.3µs align 16384 pre 1.22ms on 1.27ms post 1.21ms diff 57.8µs align 8192 pre 1.21ms on 1.28ms post 1.21ms diff 61.7µs align 4096 pre 1.21ms on 1.26ms post 1.21ms diff 41.6µs align 2048 pre 1.21ms on 1.26ms post 1.21ms diff 41.1µs $ sudo ./flashbench --findfat --fat-nr=4 /dev/mmcblk0 --blocksize=1024 --erasesize=$[2* 1024 * 1024] 2MiB 2.33M/s 4.67M/s 9.32M/s 9.57M/s 1MiB 3.4M/s 9.49M/s 9.31M/s 9.59M/s 512KiB 3.41M/s 9.54M/s 9.57M/s 9.51M/s 256KiB 4.95M/s 9.73M/s 9.63M/s 9.62M/s 128KiB 5.79M/s 9.76M/s 9.64M/s 9.72M/s 64KiB 6.04M/s 9.59M/s 9.9M/s 9.85M/s 32KiB 4.35M/s 8.92M/s 8.82M/s 8.87M/s 16KiB 2.98M/s 7.23M/s 7.25M/s 7.31M/s 8KiB 1.68M/s 4.67M/s 4.59M/s 4.62M/s 4KiB 847K/s 1.45M/s 1.56M/s 1.55M/s 2KiB 431K/s 726K/s 715K/s 736K/s 1KiB 218K/s 137K/s 137K/s 126K/s $ sudo ./flashbench --findfat --fat-nr=4 /dev/mmcblk0 --blocksize=4096 --erasesize=$[2* 1024 * 1024] --random 2MiB 2.3M/s 9.48M/s 9.29M/s 9.22M/s 1MiB 3.42M/s 5.89M/s 3.01M/s 3M/s 512KiB 4.51M/s 2.03M/s 1.85M/s 1.82M/s 256KiB 4.89M/s 1.32M/s 1.31M/s 1.31M/s 128KiB 4.93M/s 696K/s 696K/s 694K/s 64KiB 5.58M/s 850K/s 853K/s 849K/s 32KiB 4.56M/s 325K/s 326K/s 327K/s ^C $ sudo ./flashbench --open-au --open-au-nr=1 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 2MiB 8.25M/s 1MiB 2.65M/s 512KiB 2.67M/s 256KiB 2.67M/s 128KiB 4.16M/s 64KiB 9.48M/s 32KiB 8.56M/s 16KiB 6.59M/s 8KiB 4M/s 4KiB 1.32M/s 2KiB 544K/s 1KiB 14.1K/s (!!!) $ sudo ./flashbench --open-au --open-au-nr=1 /dev/mmcblk0 --erasesize=$[4 * 1024 * 1024] --blocksize=1024 4MiB 9.37M/s 2MiB 4.17M/s 1MiB 4.17M/s 512KiB 4.17M/s 256KiB 4.17M/s 128KiB 5.8M/s 64KiB 9.54M/s 32KiB 8.47M/s 16KiB 6.5M/s 8KiB 3.94M/s 4KiB 1.26M/s 2KiB 538K/s ^C $ sudo ./flashbench --open-au --open-au-nr=2 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 2MiB 5.82M/s 1MiB 3.62M/s 512KiB 1.43M/s 256KiB 658K/s 128KiB 318K/s 64KiB 232K/s ^C $ sudo ./flashbench --open-au --open-au-nr=2 /dev/mmcblk0 --erasesize=$[4 * 1024 * 1024] --blocksize=1024 4MiB 8.52M/s 2MiB 5.78M/s 1MiB 2.79M/s 512KiB 1.34M/s 256KiB 639K/s 128KiB 314K/s 64KiB 233K/s 32KiB 116K/s ^C

14 years, 3 months

Sandisk white label 2GB (from Versatile Express board)

by Arnd Bergmann

This is the first Sandisk Card that I've seen that does not have any optimizations for random access. It's particularly bad since this card was specifically shipped with a Linux box for the purpose of installing Debian on it. The label says "15 MB/s read, 7 MB/s write". Arnd --- $ head /sys/block/mmcblk0/device/{c*,scr,*rev,*id,serial,*size} ==> /sys/block/mmcblk0/device/cid <== 035344534430324780019b8975009b00 ==> /sys/block/mmcblk0/device/csd <== 002600325f5a83aefefbcfff92804000 ==> /sys/block/mmcblk0/device/scr <== 0225000000000000 ==> /sys/block/mmcblk0/device/fwrev <== 0x0 ==> /sys/block/mmcblk0/device/hwrev <== 0x8 ==> /sys/block/mmcblk0/device/cid <== 035344534430324780019b8975009b00 ==> /sys/block/mmcblk0/device/manfid <== 0x000003 ==> /sys/block/mmcblk0/device/oemid <== 0x5344 ==> /sys/block/mmcblk0/device/serial <== 0x019b8975 ==> /sys/block/mmcblk0/device/erase_size <== 512 ==> /sys/block/mmcblk0/device/preferred_erase_size <== 4194304 $ sudo ./flashbench -a /dev/mmcblk0 --blocksize 1024 --count=50 align 268435456 pre 896µs on 1.14ms post 697µs diff 345µs align 134217728 pre 671µs on 983µs post 641µs diff 327µs align 67108864 pre 748µs on 1.02ms post 615µs diff 336µs align 33554432 pre 615µs on 699µs post 582µs diff 99.9µs align 16777216 pre 671µs on 807µs post 634µs diff 154µs align 8388608 pre 759µs on 822µs post 698µs diff 93.2µs align 4194304 pre 716µs on 822µs post 692µs diff 118µs align 2097152 pre 745µs on 824µs post 701µs diff 101µs align 1048576 pre 633µs on 662µs post 669µs diff 11.5µs align 524288 pre 636µs on 668µs post 656µs diff 22µs align 262144 pre 630µs on 673µs post 657µs diff 29.6µs align 131072 pre 629µs on 673µs post 661µs diff 28.4µs align 65536 pre 640µs on 670µs post 665µs diff 17.2µs align 32768 pre 629µs on 671µs post 667µs diff 23.1µs align 16384 pre 618µs on 664µs post 658µs diff 25.5µs align 8192 pre 643µs on 643µs post 637µs diff 3.5µs align 4096 pre 657µs on 661µs post 645µs diff 10.1µs align 2048 pre 661µs on 669µs post 656µs diff 10.8µs $ sudo ./flashbench --open-au --open-au-nr=1 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 --random 2MiB 11.1M/s 1MiB 3.72M/s 512KiB 3.26M/s 256KiB 1.38M/s 128KiB 1.89M/s 64KiB 1.43M/s 32KiB 918K/s 16KiB 350K/s 8KiB 1.16M/s 4KiB 542K/s 2KiB 254K/s 1KiB 121K/s sudo ./flashbench --open-au --open-au-nr=1 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 2MiB 6.91M/s 1MiB 6.1M/s 512KiB 6.06M/s 256KiB 6.11M/s 128KiB 6.39M/s 64KiB 12.1M/s 32KiB 9.97M/s 16KiB 6.74M/s 8KiB 3.66M/s 4KiB 2.04M/s 2KiB 945K/s 1KiB 461K/s $ sudo ./flashbench --open-au --open-au-nr=6 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 --random 2MiB 11.5M/s 1MiB 10.1M/s 512KiB 7.91M/s 256KiB 3M/s 128KiB 2.2M/s 64KiB 1.21M/s 32KiB 645K/s 16KiB 310K/s 8KiB 176K/s 4KiB 86.8K/s ^C $ sudo ./flashbench --open-au --open-au-nr=6 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 2MiB 9.79M/s 1MiB 11.7M/s 512KiB 11.9M/s 256KiB 11.8M/s 128KiB 11.7M/s 64KiB 11.8M/s 32KiB 9.77M/s 16KiB 6.64M/s 8KiB 4.13M/s 4KiB 2M/s 2KiB 929K/s 1KiB 445K/s $ sudo ./flashbench --open-au --open-au-nr=7 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 --random 2MiB 12M/s 1MiB 6.1M/s 512KiB 3.23M/s 256KiB 1.55M/s 128KiB 772K/s 64KiB 384K/s 32KiB 192K/s 16KiB 95.8K/s 8KiB 47.7K/s ^C $ sudo ./flashbench --open-au --open-au-nr=7 /dev/mmcblk0 --erasesize=$[2 * 1024 * 1024] --blocksize=1024 2MiB 11M/s 1MiB 7.75M/s 512KiB 3.2M/s 256KiB 1.54M/s 128KiB 768K/s 64KiB 384K/s ^C $ sudo ./flashbench --findfat --fat-nr=4 /dev/mmcblk0 --blocksize=1024 --erasesize=$[2* 1024 * 1024] --random 2MiB 11.9M/s 12M/s 11.7M/s 12M/s 1MiB 5.54M/s 5.69M/s 5.11M/s 7.73M/s 512KiB 7.08M/s 4.65M/s 4.35M/s 4.35M/s 256KiB 6.98M/s 2.26M/s 2.27M/s 2.26M/s 128KiB 7.98M/s 5.47M/s 5.48M/s 5.47M/s 64KiB 8.4M/s 5.62M/s 5.57M/s 5.45M/s 32KiB 7.16M/s 4.89M/s 4.94M/s 4.83M/s 16KiB 5.3M/s 2.32M/s 2.32M/s 2.27M/s 8KiB 2.31M/s 2.33M/s 2.33M/s 2.33M/s 4KiB 943K/s 945K/s 942K/s 944K/s 2KiB 411K/s 408K/s 410K/s 410K/s 1KiB 190K/s 187K/s 192K/s 192K/s

14 years, 3 months

Results for danelec 16G class 4 micro SD card manfid 0x000002 oemid 0x544d

by Tim Small

root@netboot:~# (cd /sys/block/mmcblk0/device/ ; for i in * ; do if [ -f $i ] ; then echo -n "$i: " ; cat $i ; fi ; done) cid: 02544d534431364760dcbf359a00a800 csd: 400e00325b590000777f7f800a400000 date: 08/2010 fwrev: 0x0 hwrev: 0x6 manfid: 0x000002 name: SD16G oemid: 0x544d scr: 02b5800026027102 serial: 0xdcbf359a type: SD uevent: DRIVER=mmcblk MMC_TYPE=SD MMC_NAME=SD16G MODALIAS=mmc:block root@netboot:~# ~/flashbench/flashbench -a /dev/mmcblk0 --blocksize=1024 align 536870912 pre 838µs on 1.12ms post 960µs diff 222µs align 268435456 pre 859µs on 1.09ms post 955µs diff 186µs align 134217728 pre 860µs on 1.1ms post 957µs diff 196µs align 67108864 pre 861µs on 1.11ms post 957µs diff 203µs align 33554432 pre 860µs on 1.11ms post 960µs diff 197µs align 16777216 pre 861µs on 1.11ms post 953µs diff 203µs align 8388608 pre 859µs on 1.11ms post 961µs diff 198µs align 4194304 pre 863µs on 1.1ms post 925µs diff 211µs align 2097152 pre 862µs on 1.11ms post 965µs diff 199µs align 1048576 pre 954µs on 978µs post 970µs diff 15.8µs align 524288 pre 951µs on 977µs post 973µs diff 14.8µs align 262144 pre 947µs on 977µs post 967µs diff 19.8µs align 131072 pre 947µs on 983µs post 969µs diff 25.5µs align 65536 pre 951µs on 981µs post 956µs diff 26.9µs align 32768 pre 948µs on 977µs post 963µs diff 21.6µs align 16384 pre 950µs on 978µs post 950µs diff 27.7µs align 8192 pre 963µs on 960µs post 963µs diff -3106ns align 4096 pre 962µs on 969µs post 956µs diff 10.1µs align 2048 pre 963µs on 953µs post 951µs diff -3893ns >From which I guess 2M erase block size. Not sure how to interpret the last 4 rows. Only 1 open allocation unit by the look of the following :-( root@netboot:~# ~/flashbench/flashbench --open-au --open-au-nr=1 --erasesize=$[2 * 1024 * 1024] --blocksize=$[256 * 1024] /dev/mmcblk0 2MiB 3.68M/s 1MiB 3.16M/s 512KiB 3.06M/s 256KiB 3.33M/s root@netboot:~# ~/flashbench/flashbench --open-au --open-au-nr=2 --erasesize=$[2 * 1024 * 1024] --blocksize=$[256 * 1024] /dev/mmcblk0 2MiB 3.09M/s 1MiB 2.01M/s 512KiB 1.43M/s 256KiB 618K/s root@netboot:~# ~/flashbench/flashbench -f /dev/mmcblk04MiB 2.51M/s 2.46M/s 3.73M/s 3.72M/s 3.72M/s 3.72M/s 2MiB 3.7M/s 2.46M/s 3.73M/s 3.73M/s 3.72M/s 3.72M/s 1MiB 3.7M/s 2.46M/s 3.73M/s 3.74M/s 3.72M/s 3.72M/s 512KiB 3.7M/s 2.45M/s 3.72M/s 3.7M/s 3.73M/s 3.73M/s 256KiB 3.71M/s 2.63M/s 3.72M/s 3.73M/s 3.72M/s 3.72M/s 128KiB 3.71M/s 2.82M/s 3.73M/s 3.72M/s 3.72M/s 3.72M/s 64KiB 3.71M/s 3.01M/s 3.72M/s 3.72M/s 3.72M/s 3.72M/s 32KiB 3.58M/s 2.73M/s 3.57M/s 3.57M/s 3.58M/s 3.57M/s 16KiB 2.95M/s 2.25M/s 2.94M/s 2.95M/s 2.94M/s 2.95M/s The --scatter-order=<n> --scatter-span=<m> arguments are not really documented, so I didn't know how I should be using them, so I didn't. There are some strange outliers on the plot, most of which seem to end up consistently in the same place. This card has had an HD image file copied over it (with dd) prior to any of these results being generated.

14 years, 3 months

Re: [Flashbench] 2.6.38: XFS/USB/HW issue, or failing USB stick?

by Arnd Bergmann

On Friday 18 March 2011 18:45:34 Justin Piszcz wrote: > On Fri, 18 Mar 2011, Arnd Bergmann wrote: > > Getting back to the rogiinal question, I'd recommend testing the > > stick by doing raw accesses instead of a file system. A simple > > Ok, here are the results: > > root@sysresccd /root % time dd if=/dev/zero of=/dev/sda oflag=direct bs=4M > dd: writing `/dev/sda': No space left on device > 1961+0 records in > 1960+0 records out > 8220835840 bytes (8.2 GB) copied, 283.744 s, 29.0 MB/s Ok, so no immediate problem there. > > I'm also interested in results from flashbench > > (git://git.linaro.org/people/arnd/flashbench.git, e.g. like > > http://lists.linaro.org/pipermail/flashbench-results/2011-March/000039.html) > > That might help explain how the stick failed. > > Certainly, testing below, following this: > http://lists.linaro.org/pipermail/flashbench-results/2011-March/000039.html I'm sorry, I should have been more specific. Unfortunately, running flashbench is not very user friendly yet. The results indicate that the device does not have a 2 MB erase block size but rather 4 or 8, which is more common on 8 GB media. > # ./flashbench --open-au --open-au-nr=1 /dev/sda --blocksize=8192 --erasesize=$[2* 1024 * 1024] --random > 2MiB 29.5M/s > 1MiB 29.1M/s > 512KiB 28.5M/s > 256KiB 22.8M/s > 128KiB 23.8M/s > 64KiB 24.4M/s > 32KiB 18.9M/s > 16KiB 13.1M/s > 8KiB 8.22M/s > > # ./flashbench --open-au --open-au-nr=4 /dev/sda --blocksize=8192 --erasesize=$[2* 1024 * 1024] --random > 2MiB 25.9M/s > 1MiB 21.8M/s > 512KiB 15M/s > 256KiB 11.9M/s > 128KiB 12.1M/s > 64KiB 13.6M/s > 32KiB 9.81M/s > 16KiB 6.41M/s > 8KiB 3.88M/s The numbers are jumping around a bit with the incorrectly guessed erasesize. These values should be more like the ones in the first test. Can you rerun with --erasesize=$[4 * 1024 * 1024]? Also, what is the output of 'lsusb' for this stick? I'd like to add the data to https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Projects/FlashCar… > # ./flashbench --open-au --open-au-nr=5 /dev/sda --blocksize=8192 --erasesize=$[2* 1024 * 1024] --random > 2MiB 29.2M/s > 1MiB 27.8M/s > 512KiB 18.4M/s > 256KiB 7.82M/s > 128KiB 4.62M/s > 64KiB 2.47M/s > 32KiB 1.26M/s > 16KiB 642K/s > 8KiB 327K/s This is where your drive stops coping with the accesses: Writing small blocks to four different erase blocks (2MB for the test, probably larger) works fine, but writing to five of them is devestating for performance, going from 30 MB/s to 300 KB/s, or lower if you were to write smaller than 8 KB blocks. The cutoff at --open-au-nr=4 is coincidentally the same as for the SD card I was testing. This is what happens in the animation in http://lwn.net/Articles/428799/. The example given there is for a drive that can only have two open AUs (allocation units aka erase blocks), while yours does 4. > (did not run one with 7) Note that the test results I had with 6 and 7 are without --random, so the cut-off there was higher for that card when writing an multiple erase blocks from start to finish instead of writing random sectors inside of them. > # ./flashbench --findfat --fat-nr=10 /dev/sda --blocksize=1024 --erasesize=$[2* 1024 * 1024] --random > 2MiB 22.7M/s 19.1M/s 15.5M/s 13.1M/s 29.5M/s 29.5M/s 29.6M/s 29.6M/s 29.5M/s 29.5M/s > 1MiB 20.6M/s 13.3M/s 13.3M/s 20.8M/s 18.1M/s 17.8M/s 18M/s 18.3M/s 18.8M/s 18.6M/s > 512KiB 18.4M/s 18.6M/s 18.3M/s 18.1M/s 23.5M/s 23.2M/s 23.5M/s 23.5M/s 23.4M/s 23.4M/s > 256KiB 26.9M/s 21.3M/s 21.2M/s 21M/s 21.1M/s 21.2M/s 21.1M/s 21.1M/s 20.6M/s 21M/s > 128KiB 22.2M/s 22.3M/s 22.6M/s 21.4M/s 21.5M/s 21.3M/s 21.6M/s 21.3M/s 21.4M/s 21.4M/s > 64KiB 23.9M/s 22.6M/s 22.9M/s 23M/s 22.5M/s 22.4M/s 22.4M/s 22.4M/s 22.5M/s 22.4M/s > 32KiB 18.2M/s 18.3M/s 18.3M/s 18.3M/s 18.3M/s 18.4M/s 18.3M/s 18.2M/s 18.3M/s 18.3M/s > 16KiB 12.9M/s 12.9M/s 13M/s 13M/s 12.9M/s 13M/s 12.9M/s 12.9M/s 12.9M/s 12.9M/s > 8KiB 8.14M/s 8.15M/s 8.15M/s 8.15M/s 8.15M/s 8.14M/s 8.14M/s 8.15M/s 8.15M/s 8.06M/s > 4KiB 4.07M/s 4.08M/s 4.07M/s 4.06M/s 4.04M/s 4.04M/s 4.04M/s 4.04M/s 4.04M/s 4.04M/s > 2KiB 2.02M/s 2.02M/s 2.02M/s 2.02M/s 2.02M/s 2.01M/s 2.01M/s 2.01M/s 2.01M/s 2.02M/s > 1KiB 956K/s 954K/s 956K/s 953K/s 947K/s 947K/s 947K/s 950K/s 947K/s 948K/s > One thing that is very clear from this is that this stick has a page size of 8KB, and that it requires at least 64 KB transfers for the maximum speed. If your partition is not aligned to 8 KB or more (better: to the erase block size, e.g. 4 MB) or if the file system writes smaller than 8 KB naturally aligned blocks at once, the drive has to do read-modify-write cycles that severely impact performance and the expected life-time. I cannot see any block that is optimzied for storing the FAT, which is good, as this means that the manufacturer did not exclusively design the stick for FAT32, as is normally the case with flash memory cards. For this stick, I would strongly recommend creating the file system in a way that writes at least 16 KB naturally aligned blocks at all times, but I don't know if that's supported by XFS. Also, the limitation of forcing a garbage collection when writing to more than four 4 MB (or so) segments may be a problem, depending on how XFS stores its metadata. The good news is that it can do random write access inside of the erase blocks. Arnd

14 years, 3 months

Sandisk Netbook Edition 8 GB SDHC Class 2

by Arnd Bergmann

I wanted to find out if the Sandisk Netbook Edition does anything particularly well for Netbooks. Apparently this is not the case, it's a standard Sandisk Algorithm for older cards. Well, 20€ wasted ;-) This card can write random access to 6 2MB allocation units, but does not store a lookup table, so it always needs to garbage-collect the allocation unit when it does this, making random access relatively slow. Minimum size for random-access writes is 64 KB, anything smaller seems to do 64 KB copy-on-write. As a twist, it can do random access to 4 segments, but linear access to 6 segments. $ head /sys/block/mmcblk0/device/{cid,csd,scr,*rev,*id,name,serial} ==> /sys/block/mmcblk0/device/cid <== 035344534430384780708b1879009500 ==> /sys/block/mmcblk0/device/csd <== 400e00325b5900003b377f800a404000 ==> /sys/block/mmcblk0/device/scr <== 0235000000000000 ==> /sys/block/mmcblk0/device/fwrev <== 0x0 ==> /sys/block/mmcblk0/device/hwrev <== 0x8 ==> /sys/block/mmcblk0/device/cid <== 035344534430384780708b1879009500 ==> /sys/block/mmcblk0/device/manfid <== 0x000003 ==> /sys/block/mmcblk0/device/oemid <== 0x5344 ==> /sys/block/mmcblk0/device/name <== SD08G ==> /sys/block/mmcblk0/device/serial <== 0x708b1879 $ sudo ./flashbench --open-au --open-au-nr=1 /dev/mmcblk0 --blocksize=8192 \ --erasesize=$[2* 1024 * 1024] --random 2MiB 5.34M/s 1MiB 3.01M/s 512KiB 2.39M/s 256KiB 2.34M/s 128KiB 2.37M/s 64KiB 2.31M/s 32KiB 1.69M/s 16KiB 1.69M/s 8KiB 861K/s $ sudo ./flashbench --open-au --open-au-nr=4 /dev/mmcblk0 --blocksize=8192 \--erasesize=$[2* 1024 * 1024] --random 2MiB 4.08M/s 1MiB 4.96M/s 512KiB 3.05M/s 256KiB 2.36M/s 128KiB 2.33M/s 64KiB 2.3M/s 32KiB 1.91M/s 16KiB 1.61M/s 8KiB 835K/s $ sudo ./flashbench --open-au --open-au-nr=5 /dev/mmcblk0 --blocksize=8192 \ --erasesize=$[2* 1024 * 1024] --random 2MiB 3.32M/s 1MiB 4.5M/s 512KiB 3.11M/s 256KiB 2.27M/s 128KiB 2.14M/s 64KiB 1.38M/s 32KiB 715K/s 16KiB 395K/s 8KiB 193K/s $ sudo ./flashbench --open-au --open-au-nr=6 /dev/mmcblk0 --blocksize=1024 \ --erasesize=$[2* 1024 * 1024] 2MiB 5.36M/s 1MiB 5.38M/s 512KiB 5.38M/s 256KiB 5.38M/s 128KiB 5.38M/s 64KiB 5.38M/s 32KiB 4.54M/s 16KiB 3.46M/s 8KiB 2.59M/s 4KiB 1.35M/s 2KiB 631K/s 1KiB 308K/s $ sudo ./flashbench --open-au --open-au-nr=7 /dev/mmcblk0 --blocksize=1024 --erasesize=$[2* 1024 * 1024] 2MiB 5.42M/s 1MiB 4.19M/s 512KiB 2.15M/s 256KiB 1.12M/s 128KiB 583K/s 64KiB 299K/s 32KiB 152K/s ^C $ sudo ./flashbench --findfat --fat-nr=10 /dev/mmcblk0 --blocksize=1024 --erasesize=$[2* 1024 * 1024] --random 2MiB 5.29M/s 5.37M/s 5.38M/s 3.34M/s 3.33M/s 3.35M/s 3.35M/s 3.37M/s 5.33M/s 5.37M/s 1MiB 4.3M/s 4.36M/s 4.37M/s 3.26M/s 4.36M/s 2.24M/s 3.65M/s 3.49M/s 3.67M/s 3.69M/s 512KiB 3.32M/s 3.36M/s 3.36M/s 3.19M/s 3.34M/s 3.36M/s 3.35M/s 3.35M/s 3.36M/s 3.34M/s 256KiB 3.94M/s 3.95M/s 3.91M/s 3.86M/s 3.93M/s 3.94M/s 3.8M/s 3.93M/s 3.94M/s 3.92M/s 128KiB 4.35M/s 4.35M/s 4.34M/s 4.19M/s 4.34M/s 4.35M/s 4.35M/s 4.23M/s 4.35M/s 4.35M/s 64KiB 4.47M/s 4.58M/s 4.58M/s 4.46M/s 4.56M/s 4.57M/s 4.57M/s 4.48M/s 4.56M/s 4.55M/s 32KiB 3.67M/s 3.77M/s 3.73M/s 3.7M/s 3.76M/s 3.72M/s 3.76M/s 3.72M/s 3.74M/s 3.72M/s 16KiB 2.63M/s 2.64M/s 2.65M/s 2.62M/s 2.56M/s 2.61M/s 2.62M/s 2.62M/s 2.6M/s 2.61M/s 8KiB 1.45M/s 1.47M/s 1.48M/s 1.46M/s 1.45M/s 1.46M/s 1.46M/s 1.44M/s 1.47M/s 1.47M/s 4KiB 647K/s 645K/s 643K/s 644K/s 642K/s 642K/s 638K/s 637K/s 638K/s 637K/s

14 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Flashbench-results