Flashbench
Any tips about Flashbench? Googling "site:debian.org flashbench"
suggests it finds little interest in the Debian community. Thanks, ... Peter E. -- Telephone 1 360 639 0202. Bcc: peter at easthope.ca "http://carnot.yi.org/ " "http://members.shaw.ca/peasthope/index.html#Itinerary " -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4F85BAF9.7000009@easthope.ca">http://lists.debian.org/4F85BAF9.7000009@easthope.ca |
Flashbench
On Mi, 11 apr 12, 10:10:17, Peter Easthope wrote:
> Any tips about Flashbench? Googling "site:debian.org flashbench" > suggests it finds little interest in the Debian community. You assume debian-user subscribers know what Flashbench is (you could have included a link) :) In what way would you want the Debian community to be interested of Flashbench? If it is a software that could be packaged try searching for keywords 'wnpp' and 'RFP' ;) Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic |
Flashbench
On Wed, 11 Apr 2012 10:10:17 -0700, Peter Easthope wrote:
> Any tips about Flashbench? Flash-what? (sorry, couldn't resist) :-) > Googling "site:debian.org flashbench" suggests it finds little interest > in the Debian community. If you mean this tool: Tool for benchmarking and classifying flash memory drives http://git.linaro.org/gitweb?p=people/arnd/flashbench.git;a=summary I even was unaware of its existence. OTOH, it seems to consist in a bunch of files, maybe is not that hard to compile and test. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: jm6oq8$gu4$5@dough.gmane.org">http://lists.debian.org/jm6oq8$gu4$5@dough.gmane.org |
Flashbench
On 12/04/12 03:33 AM, Andrei POPESCU wrote:
You assume debian-user subscribers know what Flashbench is (you could have included a link) :) From Camaleon. http://git.linaro.org/gitweb?p=people/arnd/flashbench.git;a=summary In what way would you want the Debian community to be interested of Flashbench? I'm not advocating it. In fact I wonder what Debian people favor for investigating flash storage. Googling "site:packages.debian.org flash storage" hasn't helped. Regards, ... Peter E. -- Telephone 1 360 639 0202. Bcc: peter at easthope.ca "http://carnot.yi.org/ " "http://members.shaw.ca/peasthope/index.html#Itinerary " -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4F86F5EE.800@easthope.ca">http://lists.debian.org/4F86F5EE.800@easthope.ca |
Flashbench
On 12/04/12 07:28 AM, Camaleón wrote:
Tool for benchmarking and classifying flash memory drives http://git.linaro.org/gitweb?p=people/arnd/flashbench.git;a=summary Yes. I even was unaware of its existence. So what is your favorite software to find the erase block size of a flash storage device? Manufacturers are notoriously silent about specs. Thanks, ... Peter E. -- Telephone 1 360 639 0202. Bcc: peter at easthope.ca "http://carnot.yi.org/ " "http://members.shaw.ca/peasthope/index.html#Itinerary " -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4F86F76F.80805@easthope.ca">http://lists.debian.org/4F86F76F.80805@easthope.ca |
Flashbench
On Thu, 12 Apr 2012 08:40:31 -0700, Peter Easthope wrote:
> On 12/04/12 07:28 AM, Camaleón wrote: >> Tool for benchmarking and classifying flash memory drives >> http://git.linaro.org/gitweb?p=people/arnd/flashbench.git;a=summary > > Yes. > >> I even was unaware of its existence. > > So what is your favorite software to find the erase block size of a > flash storage device? Manufacturers are notoriously silent about specs. I don't use any, that's why I did not hear before about that tool. I still don't care much about flash based devices (neither SSD). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: jm70np$gu4$9@dough.gmane.org">http://lists.debian.org/jm70np$gu4$9@dough.gmane.org |
Flashbench
On 04/12/2012 01:10 AM, Peter Easthope wrote:
Any tips about Flashbench? Googling "site:debian.org flashbench" suggests it finds little interest in the Debian community. Thanks, ... Peter E. I got some odd results, I'm still trying to figure it all out & I'd like some help too, I'm really just sorting out my confused notes here as while I was trying to do this a couple of weeks ago my thinking jelly got ouchie, this link has helped a bit, http://blogofterje.wordpress.com/2012/01/14/optimizing-fs-on-sd-card/ one problem is I don't really see much difference in the benchmark results, probably because my benchmarking script is so rubbish the drive isn't the bottleneck. after installing git & build-essential I did mkdir ~/git cd ~/git/ git clone git://git.linaro.org/people/arnd/flashbench.git cd ~/git/flashbench/ ls #vim ~/git/flashbench/README make # simple I know but.. # find your target drive & take a note of the factory defined start sector as this is hopefully aligned on an erase block fdisk -cul # so my 32GB SanDisk Ultra SDHC card looked like Disk /dev/sdc: 31.9 GB, 31914983424 bytes 255 heads, 63 sectors/track, 3880 cylinders, total 62333952 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 8192 62333951 31162880 c W95 FAT32 (LBA) # my SanDisk USB pen drive & my Kingston SD card had a start sector of 2048 but my 120GB OCZ Agility3 had no partition table on it at all # Define variable for the target drive so commands can be pasted into a terminal window (replace X with your drive letter) trg=/dev/sdX # Backup the partition table for the target drive mkdir -p ~/backup/ umount ${trg}* dd if=${trg}* of=~/backup/${trg}_mbr_512.ddimg bs=512 count=1 # fill the start of the drive with random noise as apparently unused drives sometimes give odd numbers THIS WILL BLANK THE DRIVE, DON'T DO THIS IF THERE IS ANYTHING ON THE DRIVE YOU WANT, IN FACT YOU NEED TO UNCOMMENT THE DD COMMAND IF YOU WANT TO ACTUALLY DO IT umount ${trg}* #dd if=/dev/urandom of=${trg} bs=1M count=128 #Lets run flashbench, this is on my 32GB SanDisk Ultra SDHC card cd ~/git/flashbench/ ./flashbench -a ${trg} align 8589934592 pre 1.8ms on 2.02ms post 1.82ms diff 211µs align 4294967296 pre 1.81ms on 1.97ms post 1.76ms diff 179µs align 2147483648 pre 1.84ms on 2.03ms post 1.83ms diff 193µs align 1073741824 pre 1.82ms on 1.95ms post 1.85ms diff 117µs align 536870912 pre 1.78ms on 1.99ms post 1.87ms diff 162µs align 268435456 pre 1.84ms on 2ms post 1.83ms diff 167µs align 134217728 pre 1.8ms on 1.99ms post 1.78ms diff 203µs align 67108864 pre 1.8ms on 1.92ms post 1.83ms diff 104µs align 33554432 pre 1.78ms on 1.88ms post 1.8ms diff 91.3µs align 16777216 pre 1.79ms on 1.93ms post 1.8ms diff 134µs align 8388608 pre 1.78ms on 1.85ms post 1.73ms diff 102µs align 4194304 pre 1.79ms on 1.84ms post 1.79ms diff 54.6µs align 2097152 pre 1.8ms on 1.83ms post 1.79ms diff 32.1µs align 1048576 pre 1.82ms on 1.81ms post 1.82ms diff -9261ns align 524288 pre 1.85ms on 1.84ms post 1.83ms diff 7.86µs align 262144 pre 1.79ms on 1.82ms post 1.84ms diff 3.73µs align 131072 pre 1.8ms on 1.78ms post 1.83ms diff -30388n align 65536 pre 1.8ms on 1.79ms post 1.79ms diff -4769ns align 32768 pre 1.84ms on 1.79ms post 1.76ms diff -13269n # to help you spot where you are in the output 134217728 = 128MB & 524288 = 512k; so as the difference halves from ~100µs or more to 55µs at 4194304 = 4MB if I'm reading the README correctly this would imply that the erase block size on this card is 8MB One thing I don't understand is, if that is the case, how come the origonal partition started at 4MB 8192 * 512 = 4194304 Irrespective I now start the partition for this SD card at 16384 that way, it's allied on a 4MB & an 8MB boundary, I haven't yet figured out what open AUs are and what to do with them, I got slightly disheartened when on my OCZ SSD drive it didn't seem to make any difference to speed where I started the partition, I need to try again with a CF or SD card, maybe it was a buffering thing. That's where I've got so far, not sure I've helped you but my note are now a little more ordered. Let us know how you get on BstRgetc -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4F8A6CF4.9060407@homeurl.co.uk">http://lists.debian.org/4F8A6CF4.9060407@homeurl.co.uk |
Flashbench
On Sat, April 14, 2012 11:38 pm, Bob wrote:
> ... > # to help you spot where you are in the output 134217728 = 128MB & > 524288 = 512k; so as the difference halves from ~100µs or more to 55µs > at 4194304 = 4MB if I'm reading the README correctly this would imply > that the erase block size on this card is 8MB > > One thing I don't understand is, if that is the case, how come the > original partition started at 4MB > 8192 * 512 = 4194304 Certainly odd. No insights to offer. > Irrespective I now start the partition for this SD card at 16384 that > way, it's allied on a 4MB & an 8MB boundary, ... I'm using that idea as a temporary arrangement on a CF. > ... I haven't yet figured out > what open AUs are and what to do with them, I got slightly disheartened > when on my OCZ SSD drive it didn't seem to make any difference to speed > where I started the partition, I need to try again with a CF or SD card, > maybe it was a buffering thing. How about AU = allocation unit? No clear idea of how this relates to the HDD sector or the Flash page. > That's where I've got so far, not sure I've helped you but my note are > now a little more ordered. > > Let us know how you get on This also helped. http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device Will aim to work on it again in late May or in June. Thanks for the notes, ... Peter E. -- Telephone 1 360 639 0202. Bcc: peter at easthope.ca "http://carnot.yi.org/ " "http://members.shaw.ca/peasthope/index.html#Itinerary " -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 3875acd65a3b9a580825061f2e44871e.squirrel@easthope .ca">http://lists.debian.org/3875acd65a3b9a580825061f2e44871e.squirrel@easthope .ca |
Flashbench
On 04/18/2012 07:58 AM, Peter Easthope wrote:
On Sat, April 14, 2012 11:38 pm, Bob wrote: 8< snip 8< ... I haven't yet figured out what open AUs are and what to do with them, I got slightly disheartened when on my OCZ SSD drive it didn't seem to make any difference to speed where I started the partition, I need to try again with a CF or SD card, maybe it was a buffering thing. How about AU = allocation unit? No clear idea of how this relates to the HDD sector or the Flash page. From perusing the README it seems to be referring to the number of allocation units that can be open at any given moment without impacting performance too badly. [0] I don't know how any of that helps tho as I don't know what to do with that number, is there some-way of instructing the kernal to limit the number of open AUs? My 32GB SanDisk Ultra SDHC card, starts to slow down with 6 open AUs ./flashbench -O --erasesize=$[8 * 1024 * 1024] --blocksize=$[256 * 1024] ${trg} --open-au-nr=1 --random 8MiB 4.32M/s 4MiB 7.58M/s 2MiB 12.6M/s 1MiB 18.6M/s 512KiB 17.4M/s 256KiB 11.8M/s ./flashbench -O --erasesize=$[8 * 1024 * 1024] --blocksize=$[256 * 1024] ${trg} --open-au-nr=3 --random 8MiB 9.27M/s 4MiB 18.9M/s 2MiB 18.9M/s 1MiB 18.7M/s 512KiB 17.5M/s 256KiB 11.7M/s ./flashbench -O --erasesize=$[8 * 1024 * 1024] --blocksize=$[256 * 1024] ${trg} --open-au-nr=5 --random 8MiB 9.85M/s 4MiB 12.2M/s 2MiB 11.5M/s 1MiB 18.7M/s 512KiB 17.7M/s 256KiB 11.8M/s ./flashbench -O --erasesize=$[8 * 1024 * 1024] --blocksize=$[256 * 1024] ${trg} --open-au-nr=6 --random 8MiB 11.6M/s 4MiB 12.6M/s 2MiB 14M/s 1MiB 12.8M/s 512KiB 7.64M/s 256KiB 6.38M/s ./flashbench -O --erasesize=$[8 * 1024 * 1024] --blocksize=$[256 * 1024] ${trg} --open-au-nr=7 --random 8MiB 10.3M/s 4MiB 12.6M/s 2MiB 8.16M/s 1MiB 6.46M/s 512KiB 5.54M/s 256KiB 2.5M/s ./flashbench -O --erasesize=$[8 * 1024 * 1024] --blocksize=$[256 * 1024] ${trg} --open-au-nr=8 --random 8MiB 8.93M/s 4MiB 12.4M/s 2MiB 7.76M/s 1MiB 6.12M/s 512KiB 3.26M/s 256KiB 2.02M/s When / if I get time I'll condense this down a bit and send it into the flashbench mailing list. This also helped. http://wiki.laptop.org/go/How_to_Damage_a_FLASH_Storage_Device Will aim to work on it again in late May or in June. Thanks for the notes, ... Peter E. Thanks for the link, we'll get to the bottom of this in the end, hopefully someone who knows what's going on will put flashbench in the repositories with a good man page [0] Some not very relevant musings. Since a hard-drive cannot physically do more than one I/O at once we simulate that ability by giving them clever controllers, buffers and command queues then we more or less treat them as a black box of storage. I don't know if an individual flash memory chip can perform multiple simultaneous I/O but even if it can't, if the SSD or memory card is based on more than one chip then the question becomes can the controller support simultaneous I/O. -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 4F8E3C4F.9030900@homeurl.co.uk">http://lists.debian.org/4F8E3C4F.9030900@homeurl.co.uk |
Flashbench
These links have more information about optimizing linux with flash drives
and flashbench backround (I had this in my bookmarks) https://lwn.net/Articles/428584/ https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Projects/FlashCardSurvey -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org Archive: 20120430203440.GA3369@lisko">http://lists.debian.org/20120430203440.GA3369@lisko |
| All times are GMT. The time now is 06:11 PM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.