Extracting and Copying at the same time?

Solution
Assuming it is going to the D: drive (some extraction programs will use the windows temp directory) then yes there are likely bottlenecks somewhere and stopping one or the other will most likely speed the remaining one up. There are all sorts of potential variables at play beyond what you have put there (SATA to separate SATA drive, different partitions of the same drive, the later drive letter being a USB, the later drive letter being a network drive, the rar file being essentially uncompressed or just lightly compressed...) that could shift where the bottleneck is at. Some would have to be engineered to be that but others would be normal enough -- there have been uncompressed iso files stuck in Rar by scene groups, and you could be...

migles

All my gbatemp friends are now mods, except for me
Member
Joined
Sep 19, 2013
Messages
8,033
Trophies
0
Location
Earth-chan
XP
5,299
Country
China
it slows if you are doing the both in the same drive
read and write in an hdd are 2 different processes and the needle has to jump a lot to read or write in the 2 different places the data is located (+the place where the extracted data is being written)
keep in mind, extraction is both reading writing already.

if you are extracting in one drive and are copying files in another drives, in a modern computer it doesn't have any impact in the cpu. (of course as long as you are not running out of ram or something is wrong.)
 

FAST6191

Techromancer
Editorial Team
Joined
Nov 21, 2005
Messages
36,798
Trophies
3
XP
28,348
Country
United Kingdom
Assuming it is going to the D: drive (some extraction programs will use the windows temp directory) then yes there are likely bottlenecks somewhere and stopping one or the other will most likely speed the remaining one up. There are all sorts of potential variables at play beyond what you have put there (SATA to separate SATA drive, different partitions of the same drive, the later drive letter being a USB, the later drive letter being a network drive, the rar file being essentially uncompressed or just lightly compressed...) that could shift where the bottleneck is at. Some would have to be engineered to be that but others would be normal enough -- there have been uncompressed iso files stuck in Rar by scene groups, and you could be sticking one on a USB drive which tends to be a CPU bound process (as opposed to DMA or something else for other drive types).

You can test all this though as both extraction programs and copy programs have a pause option, or you can get a program that does have such a thing. Alternatively once things settle down speed wise then start another and watch/time the rate counters.
 
Solution

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: https://youtube.com/shorts/vKQN3UiNNHY?si=fP6ZlFe-DhQf9SW7