Issue saving across VPN

[TerryRitchie]

I have had this issue with QB64 for years, but have just finally decided to bring up the issue.

Here is where the issue happens:  I have a hardware point-to-point VPN between work and home.  I have a share set up on the server which we will call drive z:  I am running QB64 locally on my c: drive.  I open a .BAS file from drive z:, make some changes, and save it.  This is where the issue happens.  It takes FOREVER to save.  I just saved a program with 11,912 lines and it took just under 9 minutes for it to save.  Of course smaller programs take less time, but even they take a lot of time.

The VPN works great - there are no speed issues here.  I ran tests and have no issues.  Backups with large amounts of data run across the VPN late every night without issue.  If I copy the same .BAS file it completes this operation in less than 1 second regardless of direction (work>home vs. home>work) - there is something about when QB64's IDE writes the .BAS file that is causing this issue.

It is not the antivirus causing the issue either as I have tried this with the AV disabled and had the same result.

I am assuming that the system that the IDE uses to save is creating some kind of bottleneck here?  Does the save routine write and close repeatedly?  I am grabbing at straws here.

This is not a big issue since I know to avoid it so if I must work on a file locally, I will copy it, work on it, and  then send it back rather than try to save across the VPN.

Thanks,
dano

Yeah, this is odd. At first I thought this is a port forwarding issue but you said you can save the .BAS locally and then copy to the Z: drive with no issues, so that's not it.

Have you tried saving files with other programs, such as an office application, to the Z: drive? Have you noticed any slow saving with any other programs in other words?

I ran into something similar with Netware 3.12 back in the 90's and if I remember correctly it had something to do with file sharing. I had multiple people accessing a database I wrote and the performance across the drive shares was very, very slow. I seem to remember having to set something with file sharing to correct the issue but it's been so long I don't remember what I had to do.