Troubleshooting Slow Printing
on 12 August 2020 12:52 PM
“Help! I’m a print server administrator and documents are slow to print. What’s the best way to go about troubleshooting this?”
This article exists to help you determine where the slowness occurs, explains the most common causes, and how to fix them.
For testing purposes, there are two ways to remove PaperCut from the equation. It’s best to perform these tests out-of-hours to reduce the impact on your users.
Both of these methods prevent PaperCut from tracking, analyzing, or converting print jobs. In other words, the techniques help establish whether the problem is related to PaperCut, or is some other factor like printer hardware or the print server.
If PaperCut is out of the picture and the document still prints slowly, then the problem is probably unrelated to PaperCut. Please double check the list of common causes in this article.
If you find that the issue does only happen with PaperCut, then read on…
We recommend that you ONLY use the PaperCut TCP/IP port if you need it for hardware checking, and in most situations a Windows Standard TCP/IP Port will suffice.
We say this because the PaperCut TCP/IP port slows down printing by design to give the printer enough time to report how many pages were actually printed, before PaperCut will release the next print job.
Take a look through How Does Hardware Checking Affect Printing Speed for a deeper discussion on this topic.
If you’re seeing delays with releasing jobs, and you have Print Archiving switched on for your print queues, there can sometimes be delays.
Spool files are not copied to the App Server (the archive) until the job is actually released. They are not copied when the jobs are cancelled by the user, or if they time out in the hold/release queue. On slow uplinks to the application server, there can be a delay on release before the print job is sent to the destination print queue.
This can be more noticeable in Find-Me Printing Scenario with Hold/Release because the user is at the copier waiting for the job, while the job is getting copied to the File Share.
Because this is dependent on the connection speeds between PaperCut servers, there’s not much that can be done to remedy this problem aside from disabling Print Archiving, or converting that Secondary Server or Site Server to a dedicated PaperCut server.