Because of specific data sources which are available on network drives and in order to share data with colleagues I need to load data (especially Excel) from network drives and I have to save files to network drives. Unfortunately this is very, very slow.
If I compare the same file save on a local drive and on a network drive, network drive takes orders of magnitude longer than local. As a workaround, I have started to manually copy the input files from the network drive to my local harddrive, run the script and manually copy the results files to the network drive. With all the manual steps, this is still way faster than saving directly to the final destination.
I know that Excel import and export is slow, but the same happens (on a different scale) with Alteryx' native database format.
Also, I have observed that even saving the Alteryx scripts on a network drive takes very long in comparison to local save. (Gallery is not an option for me because it constantly asks my for PKI credentials.)
I have the impression that Alteryx has a fundamental problem with slow data connections/network drives.
If a direct speed up is not possible, why doesn't Alteryx just do what I do in the background: Copy the input files to a temporary directory, run the script, copy the output files back to the destination.
I would like to know if others have similar experiences and maybe workarounds/solutions.
(unfortunately, I cannot find any labels which fit to my issue.)
