I not sure if it is the best place to write about my problem but maybe Klaus or someone else will help.
I have a problem with printing pdf with text and picture. Problem is long time to wait for print.
I use network printer and socket backend in cups.
My printer understands pcl 6 so I've tested 2 divers: Generic PCL6/PCL XL Printer foomatic /pxlmono and HP Series PCL6 cups.
I've printed from xouran, evince, okular - results was the same - waiting about 5 minutes for simple one page with few text and one small picture.
The drivers I've tested had about the same performace.
In cups debug log I found that document was processed in few secons by pdftopdf filter
[11/Jul/2013:07:18:37 +0000] PID 3259 (/usr/lib/cups/filter/pdftopdf) exited with no errors.
[11/Jul/2013:07:18:38 +0000] [Job 1] Starting renderer with command: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dNOPAUSE -dNOINTERPOLATE -sDEVICE=pxlmono -r600x600 -dMediaPosition=0 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -sOutputFile=- /var/spool/cups/tmp/foomatic-7DIZyU
D [11/Jul/2013:07:22:54 +0000] PID 3260 (/usr/lib/cups/filter/foomatic-rip) exited with no errors.
So it takes over 4 minutes.
[11/Jul/2013:07:25:31 +0000] [Job 2] Running /usr/bin/gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -sDEVICE=pxlmono -sstdout=%stderr -r600 -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dMediaPosition=0 -dDuplex=false -sOUTPUTFILE=%stdout -c <</.HWMargins[12 12 12 12] /Margins[0 0]>>setpagedevice -f /var/spool/cups/tmp/gstopxl.MM0I5Q
[11/Jul/2013:07:30:02 +0000] PID 3483 (/usr/lib/cups/filter/gstopxl) exited with no errors.
also 4,5 minutes
While gs was working, CPU was almost idle so this is no cpu problem.
I strat sniffier to see what is going on in network and I've fount that when gs was working there was transfer to printer, but transfer was only about 260 kb/s in 100Mb/s network and there was no other traffic in LAN. Total transfer to printer was about 9 MB.
So I dont uderstand why it is so slow. CPU is idle network is without traffic what is case for such slowness. It is ghostscript or cups backend fault?
And what it can by done to seed up.