GitHubRulesOK
commented
2 weeks ago It should not be that slow, since a slow printer would be at least 10 ppm e.g say 6 seconds each. But it is not down to SumatraPDF which simply hands screen rendered images over to windows drivers. Thus throughput varies with every print drivers methodologies.
So for my remote PS printing it runs about 1 page per second (depending on content). Which is a reasonable 60 ppm and about as fast as most faster printers run.
Much of the time is spent in the windows spooler system, where the graphics need to be slowly converted into postscript instructions. Thus if the file was already PDF or PS it would be faster to shunt it via copy file to port or use Ghostscript conversion and bypass SumatraPDF altogether.
Have you considered Acrobat and GhostScript file handlers are more suited to "Device Printing" than MuPDF which has no inherent print engine. Windows also has native Edge print to printer which will be optimised by Microsoft to be tighter bound to the task. Throughput per page
176 pages submitted 28:13 released by windows spooler @ 37:53 Let us say that is roughly 10 minutes for about 180 pages. Thus 18 ppm as the spooler got more resource bound and slowed down as the print progressed.
So for a large file slower than 60 ppm but not as slow as 2 ppm (average page transmission roughly for 18 ppm = 12868859 baud per page so well inside comms cappacity)
Eid-Deroda
Version 3.5.2 Windows/64 bit
Printing is atrociously slow ! Two pages per minute at best ! Anyway to improve this?
Great piece of software, but might switch to an alternative if we are not able to improve printing speed.
Cheers,