Forum Discussion
All printers printing slow.
- All,
After much back-and-forth between MS and Kyocera I can confirm this painful issue has been solved.... it was indeed a firmware issue on Kyocera side. The printer was not able to communicate with the queue during sleep mode.
Not fixed yet in official firmware but will be soon I hope. I got an onofficial one...
Kr
Christiaan
MicrosoftUniPrintLad - you pose interesting questions :). To summarize the articles that Andreas shared, Universal Print has two phases:
- Service Processing time: Job going from Client to Universal Print service and getting processed in the service - this is usually very quick - within a couple of seconds. This part of journey is reflected with "upload time".
- Can you confirm how are you printing? Are you printing from Windows or have your own application that uses Graph APIs? Graph APIs can add some more time. At the end of this stage, Universal Print would have tried to inform the printer (or Connector) about job available for printing.
- Printer (or Connector), then download the job, print and update status in Universal Print. Timer for the printer/Connector starts from upload time onwards.
- Wait time: Even though the job is ready in service, in some cases printer/connector has to wait before it can process the next print job. Difference between acknowledge time and upload time indicates this wait. For e.g., in case of Connector if a printer has many jobs submitted at the same time, then jobs will be processed one-by-one at the printer. If each first job takes 7 seconds, then second job has to wait for 7 seconds. Similarly third job at the same time will have to wait for 7+7=14 seconds and so on. Having said that, concurrency of many jobs on the same printer is very rare - but it does happen!
- Printer processing time: Printer starts processing the job at "acknowledge time". Universal Print waits to hear back about job status from the printer. When printer responds saying it Completed the job, Universal Print stores that as the final time. Sometimes final time can be a bit deceptive as printer performs some finishing tasks even after printing the job.
To see the throughput of the Universal Print service, I typically look at difference between acknowledge time and created time. From your screenshot, I do not see much delays there and its usually within 3-5 seconds.
Can you confirm if you are using Connector or are you using Universal Print ready printer? Some printers can take upto 30 seconds to process a job.
P.S. - Thanks AndreasAsander for taking the lead in responding to these questions.
Hello,
We have a Kyocera TASKalfa 2554ci. This shows the same behaviour....
check out the crazy times... it is really random. and when I reboot the printer, the times are normal again....
Office personel is quite annoyed by this behaviour. Hope we can find something. We use Office applications mainly.
- Saurabh_Bansal
dacken - Can you confirm if you are using a Connector for registering printers or the Kyocera printer you mention is a Universal Print ready printer?
Saurabh_Bansal Yes confirmed. I used a printer 'unviersal printer ready'
We bought the printer because it says "Universal Print ready" on the box. We have migrated to O365 a few years ago and I literally had the old domain controller being a printer server... so I was glad to got rid of it.
it's either the pritner or the service... the big downfal is I have nothing to troubleshoot it. At least when I had a server I could look at the spool service or whatever... now it's a blackbox.
- Saurabh_Bansal
dacken - This seems like a bug and needs to be investigated. This thread does not have enough information to start an investigation.
I recommend starting with Kyocera.
- Saurabh_Bansal
dacken - if you are using Kyocera's Universal Print ready printer, have you opened a Support case with them? From your screenshot, I find no reason why printer would take so much time to acknowledge the job. Also, you mentioned that restart of the printer helped - so it seems like the printer was stuck in an unexpected state which got cleared post the reboot.