- Local time
- 4:57 PM
- Messages
- 11
It's definitely a Windows 7 problem here I can assure you! How long did the process take for you MacGyvr?
My Computer
At a glance
Windows 7 Home 64 bit
- OS
- Windows 7 Home 64 bit
not sure why the copy stops, but the reason it takes so long is that as it writes each file it verifies that the copy is 100%.
If that's the case then it seems Windows 7 is badly written software. Verifying file copy shouldn't take that long. I'm sure other operating systems are faster than Windows when it comes to copying large numbers of small files such as jpegs.
While researching this issue, it seems that Windows 7 is also slow at copying across a network too: Why is Windows 7 so slow in copying network files?
According to the research, I suspect the performance issue is related to SMB 2.0 protocol which is a new network feature in Windows Server 2008. When a user request on a Windows XP SP3 client machine go through to perform file operations over the network on a remote Windows Server 2008 file server, it will use SMB 1.0 protocol to transfer to file.
As we known, there is no way to significantly improve the performance since there are no plans to implement the necessary technologies into Windows XP. In other words, the best option to increase network performance is to upgrade to Windows Vista.
Please run the following command on the Windows Server 2008 machine to check if the network performance can be improved.
-netsh interface tcp show global
-netsh int tcp set global RSS=disabled
-netsh int tcp set global chimney=disabled
-netsh interface tcp set global autotuninglevel=disabled
Please also do not enable any services or features that your particular file server and file client do not require. These might include SMB signing, client-side caching, file system, search service, scheduled tasks, NTFS encryption, NTFS compression, IPSEC, and antivirus features.
Below there are some recommendation for TCP/IP and SMB tuning. All of these registry values are recommended based on default settings and a network with no packet loss. These registry recommendations may have the opposite effect on the network. All recommended values below are in decimal.
Subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Entry: EnableDCA
Entry: EnableTCPA
Value Type: REG_DWORD, number
Valid Range: 0,1 (False, True)
Default: 1 (True)
Recommended: 1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Interface GUID>
Entry: TcpAckFrequency
Value Type: REG_DWORD, number
Valid Range: 0-255
Default: 2
Recommended: 10-20
EnablePMTUDiscovery
Key: Tcpip\Parameters
Value Type: REG_DWORD - Boolean
Valid Range: 0,1 (False, True)
Default: 1 (True)
Recommended: 1
Description: If you set this parameter to 1 (True), TCP tries to discover the Maximum Transmission Unit (MTU or largest packet size) over the path to a remote host. By discovering the Path MTU and limiting TCP segments to this size, TCP can eliminate fragmentation at routers along the path that connect networks with different MTUs. Fragmentation adversely affects TCP throughput and causes network congestion. If you set this parameter to 0, an MTU of 576 bytes is used for all connections that are not to computers on the local subnet.
TcpTimedWaitDelay
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in seconds
Valid Range: 30-300 (decimal)
Default: 0x78 (120 decimal)
Recommended: 30
Description: This parameter determines the time that a connection stays in the TIME_WAIT state when it is closing. As long as a connection is in the TIME_WAIT state, the socket pair cannot be re-used.
According to RFC793, the value should be two times the maximum segment lifetime on the network. See RFC793 for more information.
TcpWindowSize
Key: Tcpip\Parameters
Value Type: REG_DWORD - Number of bytes
Valid Range: 0 - 0xFFFF
Default: The smaller of 0xFFFF
OR (The larger of four times the maximum TCP data size on the network OR 8192 rounded up to an even multiple of the network TCP data size.) The default is 8760 for Ethernet.
Recommended: 65535
Description: This parameter determines the maximum TCP receive window size of the computer. The receive window specifies the number of bytes a sender can transmit without receiving an acknowledgment. Generally, larger receive windows improve
performance over high (delay * bandwidth) networks. For highest efficiency, the receive window must be an even multiple of the TCP Maximum Segment Size (MSS).
TCP1323Opts
Key: Tcpip\Parameters
Value Type: REG_DWORD - 0,1,2 or 3
Default: 3
Recommended: 1 (window scale enabled only)
Description: 0 (disable RFC 1323 options)
1 (window scale enabled only)
2 (timestamps enabled only)
3 (both options enabled)
DefaultSendWindow
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD\Parameters
Value Type: REG_DWORD
Recommended: 64512
DefaultReceiveWindow
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD\Parameters
Value Type: REG_DWORD
Recommended: 64512
NonBlockingSendSpecialBuffering
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD\Parameters
Value Type: REG_DWORD
Recommended: 1
NoRemoteRecursiveEvents
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer
Value Type: REG_DWORD - 0,1
Recommended: 1
Description: Microsoft Windows NT-based and Microsoft Windows 2000-based servers continue to communicate file system changes to Windows XP-based clients even if an Explorer.exe window is not open on the client. This may cause extra traffic over a wide area network (WAN).
This issue does not occur until the Explorer.exe window on the client is opened to a share on the server and then closed.
NoRemoteChangeNotify
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Value
Type: REG_DWORD - 0,1
Recommended: 1
Description: A setting of 1 turns off Change Notify requests for file changes and for folder changes on mapped network shares. If you set this value to 1 , change notifications on network drives are disabled. You must press F5 or click Refresh on the View menu in Windows Explorer to manually update the changes in the current folder of a network share.
Please note:
When you enable the NoRemoteRecursiveEvents registry entry or the NoRemoteChangeNotify registry entry on a computer that uses a network-based configuration (for example, a %USERPROFILE% variable that points to a network drive or to a UNC path), Windows Explorer does not automatically update the display when file changes or folder changes are made by other users.
SizeReqBuf
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
Value Type: REG_DWORD
Recommended: 65535
Description: Controls the buffer size for CORE SMB requests. Setting it to 64 KB has approximately the same effect as Large Write support, which uses 60-KB buffers. This adjustment causes the server services to use more memory.
Requiresecuritysignature
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
Value Type: REG_DWORD
Recommended: 0
Description: Allows SMB to functioning without SMB signing. This allows replaying of SMB sessions and is not recommended for security reasons. Setting to 0 will allow for better performance for file sharing communication.
ReadAheadGranularity
Key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkStation\Parameters
Value Type: REG_DWORD
Default: 8
Recommended 16
Description: Number of pages to read ahead. The valid range is 0 to 16. The default setting is 8 pages (32 KB). There are few scenarios where you may have to modify the ReadAheadGranularity registry entry . For example, you may have to change this setting on a lossy WAN link or a heavily loaded Terminal server to a setting of 4 ( this setting equals a 16-KB read size).
Requiresecuritysignature
Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanworkstation\Parameters
Value Type: REG_DWORD
Recommended: 0
Description: Allows SMB to functioning without SMB signing. This allows replaying of SMB sessions and is not recommended for security reasons. Setting to 0 will allow for better performance for file sharing communication.
Hope this can be helpful.
Hi there
Just made a test using Windows explorer on a W7 x-64 machine with SP1 applied.
I've just copied an ENTIRE 1TB USB external disk (actually it had only 7GB free) so it was "Full" by any stretch of the imagination to a 2TB fixed disk I have connected to a Virtual W2K3 Server.
The Disk consisted entirely of Movies -- some in DVD ISO format and a lot in RTAV (DVD Video format).
USB disk was on a laptop connected to the LAN - the VM was connected also to the same LAN -- a proper LAN (wired) connection was used for the Laptop and the Virtual machine (Host running vmware ESXi).
I selected ALL the contents via EXPLORER and did a copy.
TWO HOURS 27 Mins (and remember this is going via a LAN and to a VIRTUAL machine via a Virtual Network card).
So I think you have a Windows problem.
BTW using the acronis backup / restore method the time was reduced to 56 mins.
Cheers
jimbo