[cups.general] Very slow document printing.

upscope upscope at nwi.net
Wed Sep 15 09:53:34 PDT 2010


Johannes Meixner wrote:

> 
> Hello,
> 
> On Sep 14 09:53 upscope wrote (shortened):
>> Johannes Meixner wrote:
>>> To analyze the printing output from a particular application,
>>> disable printing for the queue via "CUPSdisable <queue_name>"
>>> then print from the application so that the application's
>>> printing output stays as CUPS spool file
>>>    /var/spool/CUPS/d<job-number-file-number>
>>> until you re-enable printing "CUPSenable <queue_name>".
>>
>> It maybe I have not waited long enough in past.
> 
> If it takes a long time until the printing output from a particular
> application appears as CUPS spool file, it is first and foremost
> the application which needs so much time to produce its printing
> output which usually depends on the application's input data.
> 
> Afterwards (after "CUPSenable <queue_name>") the printing system
> may actually print it quickly or also need much time to print it
> depending on the size and content of the application's printing
> output and depending on the used printer driver and its settings
> for this particular print job e.g. low resolution b/w printout
> versus high resolution photo quality printout.
> 
> Finally depending on which printer model is used, the printer
> may actually print it fast or also need much time to print it
> depending on the size and content of the printing system's
> printer-specific output and depending on the available memory
> and computing power inside the printer and its mechanical
> capabilities (low-cost printer versus high-end PostScript printer).
> 
> You may have a look at
> http://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility
> ------------------------------------------------------------------
> Though 1200 dpi provides hardly any visible improvement
> over 600 dpi, it consumes four times as much CPU performance
> and memory than 600 dpi.
> ...
> A bitmap image at 1200 x 1200 dpi consumes 16 times more memory
> than it would at 300 x 300 dpi. A color depth of 32 bits
> consumes 32 times more memory than 1-bit b/w mode.
> Accordingly, a bitmap image at 1200 x 1200 dpi
> and 32-bit color depth consumes 500 times more memory than
> the same image in 1-bit b/w mode at 300 x 300 dpi resolution.
> ------------------------------------------------------------------
> 
> 
> Kind Regards
> Johannes Meixner
I agree with everything you say. My printers default resolution is 150. 

I looked at the held file and the c00089 file has the following for 
resolution:
  Resolution^@^A^AD^@^E (Not sure what the encoded characters mean).

In the d00089-001 I have not figured out what the resolution is.

As for the actual document I only choice page 1 of 6. It appears in the CUPS 
jobs almost instantly. It is when CUPS shows processing it takes forever. I 
have run this job using CUPS for the last 4 years. To my knowledge the 
download file format has not changed. CUPS version have and with 1.4.3 the 
original PPD changed from a Xerox supplied one to a linuxprinting one as the 
old one no longer works. I will run the PPD test on both PPD's. Don't no if 
the problem is the newer versions of openSUSE, the PPD or CUPS 1.4.4 which I 
am presently using with openSUSE 11.3 and 11.4 MS1.

I don't think memory is a problem, I have 2.4GB free memory.

I appreciate your help and through explanations.

 -- 
Russ
openSUSE 11.3 (2.6.34-12-default)|KDE 4.5.1|
Intel core2duo 2.5 MHZ,|4GB DDR3|GeForce 8400GS 




More information about the cups mailing list