G
Guest
I have a C# client app that sometimes needs to do thousands of specialized
file renames of files on a file server in the same domain. If the files
reside locally on the client machine, the renames take only a few seconds.
If the files reside on the file server, a set of 30,000 file renames may take
a half hour to do.
I'm just using File.Move to do the rename. The renames are not moving the
files to a different folder, they are just changing the name of the file.
I'm assuming that network latency between each of the File.Move calls is
what is slowing the renaming down so much.
Is there a way to batch up all 30,000 File.Move commands to the server,
rather than sending them each one at a time so that I am not paying the price
of the network latency between every single file rename? Or is there a
better way to speed this up? It needs to be almost as fast as doing it
locally on the client.
file renames of files on a file server in the same domain. If the files
reside locally on the client machine, the renames take only a few seconds.
If the files reside on the file server, a set of 30,000 file renames may take
a half hour to do.
I'm just using File.Move to do the rename. The renames are not moving the
files to a different folder, they are just changing the name of the file.
I'm assuming that network latency between each of the File.Move calls is
what is slowing the renaming down so much.
Is there a way to batch up all 30,000 File.Move commands to the server,
rather than sending them each one at a time so that I am not paying the price
of the network latency between every single file rename? Or is there a
better way to speed this up? It needs to be almost as fast as doing it
locally on the client.