Dec 12, 2019
9
0
10
Let's say hypothetically i have 2 HDD , one is faster than the other .If i merge them into one Local disk , what happens with the speed of the both ? Im wondering , for example i download something which is 120gb into the merged disk and then i decide to copy it to somewhere else and because of the 2 HDD with different speed , 50 % (60gb) will be transfered faster and the other 50% slower ?
How is it working ?
 
Solution
Let's say hypothetically i have 2 HDD , one is faster than the other .If i merge them into one Local disk , what happens with the speed of the both ? Im wondering , for example i download something which is 120gb into the merged disk and then i decide to copy it to somewhere else and because of the 2 HDD with different speed , 50 % (60gb) will be transfered faster and the other 50% slower ?
How is it working ?
It depends on how you "merge" them. Do you stripe them? Concatenate them? Mirror them? Use the fast one as a buffer for the slow one?

Based on your copy scenario, you are striping them. You should expect your ENTIRE copy to be at the slowest speed. Why? Lets say byte (or Kbyte) 1 is on "fast" and byte (or...

kanewolf

Titan
Moderator
Let's say hypothetically i have 2 HDD , one is faster than the other .If i merge them into one Local disk , what happens with the speed of the both ? Im wondering , for example i download something which is 120gb into the merged disk and then i decide to copy it to somewhere else and because of the 2 HDD with different speed , 50 % (60gb) will be transfered faster and the other 50% slower ?
How is it working ?
It depends on how you "merge" them. Do you stripe them? Concatenate them? Mirror them? Use the fast one as a buffer for the slow one?

Based on your copy scenario, you are striping them. You should expect your ENTIRE copy to be at the slowest speed. Why? Lets say byte (or Kbyte) 1 is on "fast" and byte (or Kbyte) 2 is on "slow". The OS will wait for several of those bytes (or Kbytes) to be read into memory before starting the copy. Therefore everything is limited to the slowest disk.
 
  • Like
Reactions: Vicho Bucho
Solution
Dec 12, 2019
9
0
10
It depends on how you "merge" them. Do you stripe them? Concatenate them? Mirror them? Use the fast one as a buffer for the slow one?

Based on your copy scenario, you are striping them. You should expect your ENTIRE copy to be at the slowest speed. Why? Lets say byte (or Kbyte) 1 is on "fast" and byte (or Kbyte) 2 is on "slow". The OS will wait for several of those bytes (or Kbytes) to be read into memory before starting the copy. Therefore everything is limited to the slowest disk.

Interesting . Also now i checked and if I right click over the unallocated space and "New stripped volume " is grey and the others aswell except "New simple volume"
I found another problem , when i press "new simple volume " it says There is not enough space available on the disks to complete this operation But only to the one unallocated space. i have 2 by 232gb unallocated space from 1 disk.


EDIT: I found a way but not with Windows build in disk management , it wasnt allowing me to merge completely 1 HDD into one partion.I did it with EaseUs.
 
Last edited: