Big gap between read and write speeds of a pen drive
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Big gap between read and write speeds of a pen drive
Hello, I have a pen drive and after running a benchmark, it says my pen drive has a write speed of only 1.1 Mb/s on average, against 13.5Mb\s of average read speed. I found the write speed surprisingly low and started to inquire myself if there could be something wrong with my linux distro (an ubuntu 10.04).
My personal experience says that the results of the benchmark are consistent with what I see on daily use.
You think it's worth try with another linux distro or is just it's flash memory that it is crap?
I tested on live disc and the performance seemed similar to the one informed by the benchmark (it was a slax distro and the file manager doesn't tell the average transfer speed).
I checked this site: http://usbspeed.nirsoft.net/ with hundreds of results, and no one has a result anywhere near 1.1Mb/s of write speed. If i didn't skipped any result, the slowest I saw was 2.96Mb/s , which is approximately 2.7 faster than mine. Very strange.
Maybe it's a defect, sometimes other computer can't read it's contents.
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,673
Rep:
OK, here's my take on this. I've no idea how data is read or written to a USB pen drive but as a retired Computer hardware maintenance engineer I'll pass on a theory for consideration...
In the "bad old days" of magnetic media; disks, tapes, etc, reading data was just that, the data was read, moved to memory and manipulated, no state changes in media required. Writing data was different as, after the data had been written (with relevant "bit" state changes), it had to be read back and verified. This means that a write function also contained a read function hence it takes longer to carry out. Subsequently, the write function takes more processor cycles than a read one does.
Anyway, that's my thoughts. Non-static volatile memory is different as it requires refresh cycles to constantly read and write its cell states in order to maintain the data's integrity.
Oftentimes, even the manufacturers will report speeds of i.e. 20MB/sec write and 60MB/sec read. The flash memory chips are just a great deal faster on write. When you read, there's no change to the data. When you write, it has to check for errors, manipulate bad blocks, adjust the write location for the sake of wear leveling, and (if you're not using FAT or ext2) it must write a journal besides.
In the "bad old days" of magnetic media; disks, tapes, etc, reading data was just that, the data was read, moved to memory and manipulated, no state changes in media required. Writing data was different as, after the data had been written (with relevant "bit" state changes), it had to be read back and verified. This means that a write function also contained a read function hence it takes longer to carry out. Subsequently, the write function takes more processor cycles than a read one does.
Anyway, that's my thoughts. Non-static volatile memory is different as it requires refresh cycles to constantly read and write its cell states in order to maintain the data's integrity.
Aaaah, takes me back to the days when you had to consider bits in order to complete a program...no much was done for you (no code completion, no backgroud safety nets, none of that) so it was the same cycle all the time idea -> paper -> writein (yes, more paper) out the code -> typing in -> saving (in case the code 'd lock up the system) -> crossing fingers -> running...
Aaahhhhh....where are the days....
Melissa
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.