TCP/IP Printing Causes File Cache to Grow

 Last reviewed: July 24, 1997
Article ID: Q149658
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

If you transfer large print jobs via LPR/LPD either from a Windows NT computer to an LPD printer or from some other system to the LPD service, you notice a user interface performance degradation. The jobs need to have about the size of the physical memory of the computer.

If you look at performance counters while this happens, you find that the counter for the file cache (Memory: Cache Bytes) is very high while the process working sets decline (Process: Working Set, instance _Total).

CAUSE

While copying spool files, the TCP/IP printing components do not use the flag FILE_FLAG_SEQUENTIAL_SCAN to open the files. Thus, cache manager increases the cache size when data is read or written because it expects the application to need it again.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords : kbbug4.00 kbfix4.00 kbprint ntprint NTSrvWkst kbbuglist kbfixlist
Version : 4.0
Platform : winnt
Issue type : kbbug
Resolution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.