Forum Discussion
Slow print, many failed print jobs.
we are experiencing the same issue.
Since the product is out of the public preview its horrible slow. a simple testpage takes up to 3 minutes to get spooled.
We are thinking to downgrade back to the Hybrid Cloud print Solution. that worked fast ...
Erik_Schuiling One of the factors that impact job latency is the time to upload and download documents from cloud. What is the payload size for your documents?
3 minutes is large if its happening on regular basis? How busy are your printers. Currently, for a single printer on Universal Print connector jobs are processed one after another. Sometimes this can cause delay if the previous job on same printer is delayed.
Last thing to check is printer status.
mrkitty are you still seeing latency issues? Can you reach out to Microsoft Support if you continue to see 503s?
Thanks
Saurabh
- Erik_SchuilingNov 02, 2021Copper Contributor
we had raised a support request and Microsoft confirmed there was a performance issue.
We created now multiple print queues to speed up the process.
- radwanFeb 15, 2022Copper ContributorI can only confirm the problems with the speed of the MUP. We have several customer installations with the MUP and with all installations it takes between 3-5 minutes for a normal print job (1-3 pages) until the print job is available. Since we always have uniFLOW behind the MUP as a FolowMe solution, the users hardly notice this problem, but the problem is definitely present and has nothing to do with the speed of the connection to the cloud. We would be very grateful for any ideas that could contribute to the solution.
- mrkittyFeb 15, 2022Copper ContributorWe haven“t had any issues since November 2021. Neither Microsoft or myself ever found the reason for the slow prints and failing print jobs, but for some reason, it just started working and has so ever since.
- mrkittyNov 01, 2021Copper ContributorI have reached out to Microsoft Support. At the moment UniversalPrint works fine, so for now our fingers are crossed that it will keep working.
Despite the logs are still marking several errors, there is nothing to explain the slow and failing jobs we saw.