LAN上的远程文件操作效果 [英] Remote file manipulation effect on LAN

问题描述

你好



i需要将多页（tiff）文件复制到远程NAS存储器，并将每个tiff拆分成单独的图像。



代码作为C＃桌面应用程序在与NAS存储在同一LAN上的机器上执行



我访问使用带有凭证的NetworkConnection类的远程存储，我使用了这个类：



https ：//gist.github.com/AlanBarber/92db36339a129b94b7dd



我的问题是：



哪个更好，影响网络流量少？首先将（tiff）文件拆分为图像，然后将这些图像复制到远程存储中？或者先复制副本然后再进行拆分？



我尝试了什么：



i被告知在远程存储上执行（拆分）操作实际上会检索远程文件的副本以在本地操作它，然后通过流返回结果。我认为这会在网络上增加不必要的流量。



因此我更改了代码以先进行分割，然后进行复制，但是用户没有注意到改进在表现





你怎么看？

hello

i need to copy multi-page (tiff) files to a remote NAS storage, and split each tiff into separate images.

the code is executed as a C# desktop application on a machine that is on the same LAN as the NAS storage

I access remote storage using NetworkConnection class with credentials, i used this class:

https://gist.github.com/AlanBarber/92db36339a129b94b7dd

my question is :

which is better and affects the network traffic less ? splitting (tiff) file into images first, and then copying these images to remote storage? or doing the copy first and the splitting next?

What I have tried:

i was told that performing a (split) operation on remote storage actually retrieves a copy of the remote file to manipulate it locally and then returns result by streaming. and i think that adds unnecessary traffic on the network.

so i changed the code to do the splitting first, then the copying, but users haven't noticed an improvement in performance


what do you think?

推荐答案

至少流量将在本地复制文件，拆分成单个文件，然后将拆分文件复制回NAS。



这绝不意味着您将获得更好的性能，但只有最少的流量。

The least amount of traffic is going to be copying the file locally, doing the split into individual files, then copying the split files back to the NAS.

This in no way means that you're going to get better performance, but only the minimum of traffic.

这篇关于LAN上的远程文件操作效果的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！