Dec 13 2023 01:10 PM
As seen above many print jobs are taking +30 seconds regularly to print. Printer acknowledgement time is oddly high in this case but among other printers (we have +50 using universal print, all very slow when compared to operating on local network) the time delay may be more due to upload/download. The larger file sizes on average take longer as expected but not in all cases, some times very small 1 page print jobs just take a long time despite the printer not doing anything when the job was issued.
Dec 13 2023 10:28 PM
Jan 05 2024 08:20 AM - edited Jan 05 2024 08:23 AM
Thank you for the response and documentation. While it does grant me insight into the process, my goal is to improve these time metrics as the business which is piloting Universal Print prints thousands of pages a day; many individual user workflows will exceed 100+ individual print jobs per day. So, going from a 2 second response to a 45 second response for each one is simply not viable to sustain their workflow. Naturally we can try to reduce the need for such high printing traffic, but the point of Universal Print is...to print, I believe - and the organization is very interested in continuing to print at the same rate for now.
Universal Print is failing to "keep up" with their printing traffic needs, essentially.
The printer management benefits on the other hand are quite useful to the organization so if I am able to improve the print times in any manner then it is still possible to retain their use of Universal Print.
While I know you have implied that we cannot expect any improvement in performance from Microsoft's end on this in the near future, I am hopeful that you can disclose what type of network traffic Universal Print uses so that we may attempt Quality of Service and traffic shaping measures to improve these slow print times.
Any other tactics which you may recommend beyond "don't use the connector" would also be welcome; I only use the connector for models which do not support universal print, however, in my experience the print times are not noticeably different regardless of whether the connector is in use or not.
Jan 07 2024 10:56 PM
Here is an article published by Microsoft themselves which discusses the topics I linked previously but more in depth.
To be more specific the article goes through each step of the "print job journey" and the impact each step has on the latency of a print job which in turn points you to where you can make improvements to reduce the bottlenecks.
Keep business going with Universal Print - Microsoft Community Hub
Jan 11 2024 09:37 PM
@AndreasAsander
I really appreciate your response.
Jan 18 2024 07:23 AM
@UniPrintLad - you pose interesting questions :). To summarize the articles that Andreas shared, Universal Print has two phases:
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.
Jan 22 2024 07:49 AM
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.
Jan 22 2024 09:47 AM
@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?
Jan 22 2024 10:03 AM
@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.
Jan 26 2024 01:19 AM - edited Jan 26 2024 01:23 AM
@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.
Jan 26 2024 09:49 AM
@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.
Jan 30 2024 11:33 AM - edited Jan 30 2024 11:34 AM
Hi,
This is Kevin from Kyocera Document Solutions Development America.
We are currently investigating this issue.
We will provide an update regarding this issue after ongoing investigation, and will also provide an update on how to contact the correct communication channel with Kyocera support soon.
Regards,
Kevin
Jan 31 2024 12:07 AM
Mar 26 2024 04:37 AM
SolutionMar 26 2024 04:37 AM
Solution