Allocation of Print Server Threads May Cause DelaysLast reviewed: February 17, 1998Article ID: Q180954 |
The information in this article applies to:
SYMPTOMSThe Host Print service's method of allocating threads may result in poor printing performance if a network printer is extremely busy or becomes unavailable for some reason.
CAUSEThe Host Print service currently allocates one thread for every 32 print sessions. In this case, if one printer is slow to respond or is unavailable, the other print sessions running on the same thread may experience performance degradation.
STATUSMicrosoft has confirmed this to be a problem in SNA Server Versions 3.0, 3.0 SP1, 3.0 SP2, and 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.
MORE INFORMATIONWith the fix applied, thread allocation is changed to allow for Print Server to run 1 thread per session for up to 32 sessions. The next 32 sessions will be run at 2 sessions per thread increasing up to 32 sessions per thread. By running fewer sessions per thread, potential delays will be minimized. Keywords : kbbug3.00 kbbug3.00.sp1 snaprintservice kbbug3.00.sp2 kbbug4.00 kbprint Version : WINDOWS:3.0,3.0SP1,3.0SP2,4.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |