New
#11
Is the write speed of the receiving hdd that limiting factor or the write speed of the sending hdd?
And how does the 32MB or 64MB of cache on the hdd affect it?
Is the write speed of the receiving hdd that limiting factor or the write speed of the sending hdd?
And how does the 32MB or 64MB of cache on the hdd affect it?
the write speed of the receiving hdd is the usually the limiting factor in large file transfers between HDDs with the same interface (sata, pata, IDE ..etc) and rpm. Cache size is a factor in the read/write speeds, acts as a buffer to reduce the number of reads/writes
Thanks.
What about RPM? Does it come into play to a greater effect than write speed?
Faster spinning HDDs as a rule will read/write faster. Most desktop HDDs under 1GB are 7200 rpm. A 1gb caviar green spins @ 5400 rpm whereas a caviar black runs at 7200 rpm, and that's the main reason your caviar green can't be written to as quickly as your other HDD.
you are all wrong, i know for a fact the thing that defines the speed is pixie dust.
lmao... thread solved
You're welcome..
I've had to explain the same thing quite a few times over the years.. and in reality, fragmentation is not much of an issue unless the gaps between the fragments are huge and the fragments themselves are numerous and non-sequential. The typical linux system partition for example, would look horribly fragmented to a windows based defragmenter if windows could recognize the ext file system, but 64 bit ubuntu (gnome, lucid edition 10.4 to be specific) has approximately the same system load as windows xp and runs much more quickly and efficiently simply because the files are not in contiguous blocks on the HDD