11-07-2023, 03:43 AM
I run lots of stuff off a networked drive, similar to what you're describing, and one thing I've noticed is that these modern drives like to put themselves into sleep mode. Whenever I go to access that networked drive the first time, it has to wake itself back up, get those platters spinning, get up to speed, and then make everything accessible to the OS -- which takes about half a minute or more on my system. Once it's up and going, there's no problem with access times or transfering data, but there's that initial start-up time involved with the process.
With QB64, this would lead to it taking a minute to save a single file (as the drive had to awaken and come online), whereas, like you, late at night I could do large file transfers without any issue. (After all, what's a 30 second wake up time when transfering 200GB of data over an hour?)
I'm wondering if something similar is happening for you. Is the system taking an excessive amount of time to wake up that drive and get it transfer ready? One easy test for such a thing would be to save the file, let it take X minutes to do its thing, and then try to resave the file and see if that transfer rate has went back down to something reasonable. After all, the first save would be one to awaken the device, so the second attempt at saving should take that time out of the transfer equation, leaving you with a better idea of how fast you're actually moving the data across the network.
With QB64, this would lead to it taking a minute to save a single file (as the drive had to awaken and come online), whereas, like you, late at night I could do large file transfers without any issue. (After all, what's a 30 second wake up time when transfering 200GB of data over an hour?)
I'm wondering if something similar is happening for you. Is the system taking an excessive amount of time to wake up that drive and get it transfer ready? One easy test for such a thing would be to save the file, let it take X minutes to do its thing, and then try to resave the file and see if that transfer rate has went back down to something reasonable. After all, the first save would be one to awaken the device, so the second attempt at saving should take that time out of the transfer equation, leaving you with a better idea of how fast you're actually moving the data across the network.