Large File Copy Operation Causes Available Bytes to Drop Significantly (191098)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q191098 SYMPTOMS
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.
CAUSE
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.
RESOLUTIONTo 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, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSMicrosoft has confirmed that this is 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.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB191098 |
|---|
|