为什么在远程计算机上本地复制文件这么慢?

发布于 2024-11-01 03:20:54 字数 588 浏览 1 评论 0原文

假设我有 \machinename\dll。我在 Windows 资源管理器中打开 \machinename,然后在 dll 文件夹上进行复制/粘贴以制作它的备份副本,这样 \machinename 中就会有一个“dll - Copy”文件夹。速度慢得可怕。我听说 Windows 实际上将文件夹/文件复制到我的本地计算机,然后将它们复制回来。为什么?

我们可以使用 RDP 远程访问服务器来进行更改,但当我从家里通过 VPN 连接时,我真的不喜欢在另一个 RDP 会话中使用 RDP。

为什么远程服务器不能知道我正在尝试复制文件,而是在本地进行复制,而不是将所有内容复制给我,以便我可以将其复制回来?

回答

http://computer-vet.com /weblog/2008/01/28/remote-command-line-on-windows.html

我测试了它,它工作得非常好。它就像命令提示符的远程桌面。赢!

Let's say I have \machinename\dll. I open \machinename in Windows Explorer and do a copy/paste on the dll folder to make a backup copy of it so there will be a "dll - Copy" folder in \machinename. It's horrendously slow. I hear that Windows actually copies the folder/files to my local computer then copies them back. Why?

We can use RDP to remote into the server to make the changes, but I really don't like using RDP within another RDP session when I am connected via VPN from home.

Why can't the remote server know I am trying to copy a file and just do the copy locally on its end rather than copying everything to me just so I can copy it back?

ANSWER!

http://computer-vet.com/weblog/2008/01/28/remote-command-line-on-windows.html

I tested it and it works awesomely. It's like remote desktop for command prompts. WIN!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

鯉魚旗 2024-11-08 03:20:54

人类概念上认为的“复制功能”是由程序执行的。通过从本地计算机启动复制功能,程序将在本地计算机上运行。然后,它从当前位置读取每个文件和文件夹,并将其写入目标位置。复制程序不知道也不关心源和/或目标是本地还是远程。您的情况下的数据流是这样的:

[remote disk] -> [network] -> [local RAM] -> [network] -> [remote disk]

复制速度非常慢,因为所有数据都必须通过网络发送两次。

如果程序被编程为检测远程->远程复制,并更有效地执行该操作,那么速度会更快——可惜事实并非如此。

但您已经知道解决方案:通过在存储文件的计算机上启动复制功能,将“网络副本”变成“本地副本”。

What a human conceptually thinks of as a "copy function" is performed by a program. By initiating the copy function from your local computer, the program is run on your local computer. It then reads each file and folder from its current location, and writes it to the destination location. The copy program doesn't know and doesn't care whether the source and/or destination are local or remote. The data flow in your case is thus:

[remote disk] -> [network] -> [local RAM] -> [network] -> [remote disk]

The copy is so slow, because all of the data has to be sent over the network twice.

If the program had been programmed to detect a remote->remote copy, and perform that more efficiently, it would be faster - alas it wasn't.

But you're already aware of the solution: turn the "network copy" into a "local copy" by starting the copy function on the machine where the files are stored.

待"谢繁草 2024-11-08 03:20:54

http://computer-vet.com /weblog/2008/01/28/remote-command-line-on-windows.html

我测试了它,它工作得非常好。它就像命令提示符的远程桌面。赢!

http://computer-vet.com/weblog/2008/01/28/remote-command-line-on-windows.html

I tested it and it works awesomely. It's like remote desktop for command prompts. WIN!

橪书 2024-11-08 03:20:54

尝试在远程 moshine 上使用另一个 shell 指挥官(例如总指挥官或其他...指挥官)。或者您可以尝试不使用快捷键 ctrl+c/v 而是使用鼠标拖动来复制文件/目录(也可以按 Shift 键进行复制)。

Try using another shell-commander (like, total commander or other ...commander) at remote moshine. Or you can try to copy file/dir not with shortcut ctrl+c/v but with mouse dragging (for copy press shift also).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文