Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
FWIW, Windows 10 has the pause/play functionality you mentioned built in to Explorer.
Hehehe....I was thinkin' the same thing.
I attempted to upgrade to Windows 10 to check it out back in April IIRC. It bricked my installation of Windows. Couldn't recover, couldn't repair my 7 install... it was just completely fubar. I'm not that torn up over losing the pause functionality. I honestly don't do as much moving of files as I used to. TeraCopy was just nice to have.
I'm not ready to dive into Windows 10 yet. It is causing me more headaches at work and at my own business than it has relieved so I personally do not want to be dealing with them on my own home front. Windows 7 has served me extremely well and has been incredibly stable for everything I do.
Any chance your Virus protection is running a scan before proceeding with the paste function?
Should you choose to nuke Win7 to reinstall it, Secure Erase the SSD before. Might help restore some preformance.
I was looking to see if anyone had mentioned that. I'm wondering if it is possible that some AV S/W is trying to scan the new files as they are copied.
The other thing I see is that drives are relatively full. SSDs can operate faster if there is empty space. Unlike an HDD, once sectors on the SSD are written, they have to be erased before they can be written again. On a drive with a lot of free space there is usually adequate erased space available. As a drive fills up this effect can slow things down. But I suppose the target drive starts out with adequate free space. If there are a lot of files - particularly small files - the drive can experience write amplification. If a file (or directory entry) smaller than the SSD's block size is written, the entire block has to be erased and rewritten along with the new data.
You freed up a bunch of space on the Intel drive and then copied files to that? Perhaps the free space had not yet been erased. Has anyone mentioned TRIM in this thread? That's a way for Windows to tell the drive that disk blocks are no longer in use and can be erased to prepare for the next write. I've heard that it is no longer needed for modern SSDs but I don't know how the drive controller would know a block is no longer in use. I suppose it would depend on the SSD controller understanding the filesystem that the OS is using.I was afraid that a lack of free space was causing the massive slow downs, but even once the space was freed the transfers were still slow moving from the OCZ to the Intel when using TeraCopy. Disabling TeraCopy for whatever reason and using the Windows explorer solved the issue. Now file transfers are back to their normal rates (300-450MB/s).
Is it possible that the Intel drive controller sacrifices highest potential speed to gain better 'real world' performance? Maybe it does a better job of detecting and erasing unused blocks.I don't have an answer as to why yet. It's seems odd that it only affects transfers only one way between two specific drives. In this case inbound on the Intel from the OCZ. I assume it's just the version of the program. I will download a different version tomorrow and try that just to see if that was the case. I am curious as to what may actually be the issue and am going to find more confirmation on what it is.
You freed up a bunch of space on the Intel drive and then copied files to that? Perhaps the free space had not yet been erased. Has anyone mentioned TRIM in this thread? That's a way for Windows to tell the drive that disk blocks are no longer in use and can be erased to prepare for the next write. I've heard that it is no longer needed for modern SSDs but I don't know how the drive controller would know a block is no longer in use. I suppose it would depend on the SSD controller understanding the filesystem that the OS is using.
Is it possible that the Intel drive controller sacrifices highest potential speed to gain better 'real world' performance? Maybe it does a better job of detecting and erasing unused blocks.
Glad to hear that you're making progress on this.