Large File Copy Operation Causes Available Bytes to Drop SignificantlyID: Q191098
|
A large file copy operation causes available bytes to drop significantly.
This happens when a Windows client copies a large file from or to a Windows
NT computer.
In this case, you will notice a user interface performance degradation. The
files need to be about the size of the physical memory of the computer or
greater.
If you look at performance counters while this happens, you find that the
counter for the file cache (Memory: Cache Bytes) goes up while the process
working sets (Process: Working Set, instance _Total) decline. Available
bytes (Memory: Available Bytes) declines in the inverse proportion of the
cache bytes.
While copying the files, Windows clients do not use the flag FILE_FLAG_SEQUENTIAL_SCAN to open the files. Thus, Cache Manager tries to cache the whole file in memory and causes the file cache to grow and, thus, available bytes to drop.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the
Microsoft Knowledge Base:
Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Keywords : NT4SP4Fix kbbug4.00 kbfix4.00.sp4
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug
Last Reviewed: April 10, 1999