desktop-packages team mailing list archive

[Dean Montgomery <463059@xxxxxxxxxxxxxxxxxx>]

Resolved this issue by lowering and creating custom DPI values.

Default DPI from foomatic postcript PPDs is usually 600 DPI or 1200 DPI.
Ghostscript `pdftops` and `gs` both take a long time converting high DPI
values.  The 600 DPI also creates a large postscript file which in turn
are slow over the network as well as slow spooling on the printer
itself.  Printers have low RAM & small CPU.

When I lowered DPI to 300 the print jobs were almost instantaneous.
However the print quality was degraded.

I modified the PPD files for dozen or so laser printers and found that
400DPI is identical to 600DPI in terms of print quality.  With our
printers I found the "sweet spot" to be 350DPI for print quality and
maximum speed.

To get custom "time/quality sweet spot" DPI values, you will need to edit your PPD file:
cp /etc/cups/ppd/MYPRINTER.ppd $HOME/
Edit MYPRINTER.ppd  'Resolution' section and add 350 and 400 DPI.

*DefaultResolution: 350x350dpi
*Resolution 150x150dpi/150x150 DPI: "<</HWResolution[150 150]>>setpagedevice"
*Resolution 300x300dpi/300x300 DPI: "<</HWResolution[300 300]>>setpagedevice"
*Resolution 350x350dpi/350x350 DPI: "<</HWResolution[350 350]>>setpagedevice"
*Resolution 400x400dpi/400x400 DPI: "<</HWResolution[400 400]>>setpagedevice"
*Resolution 600x600dpi/600x600 DPI: "<</HWResolution[600 600]>>setpagedevice"

You may want to update the ModelName, ShortNickName and NickName to
indicate that this file has been modified.

You can then either use the web interface to upload your custom ppd file or copy it to /usr/local/share/ppd/MYPRINTER.ppd
Then restart cups service.  Your custom PPD option will then appear in the pick-list when Modify Printer.

Once the PPD is installed then go to the Default Options to set the DPI
Resolution.   You may want to test the timing/quality for 300, 350, 400,
600.  I had 2 printers where 300DPI quality was just as good as the 600
DPI.

If an end-user enjoys the long print delay so they can socialize at the
printer - or enjoys burning CPU cycles imagining that their 1200dpi is
actually "better quality",  then all they have to do is increase the DPI
setting on the print dialog before they send their job.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to foomatic-filters in Ubuntu.
https://bugs.launchpad.net/bugs/463059

Title:
  Process 'gs' begins taking 100% CPU and loading up vast amounts of RAM

Status in foomatic-filters package in Ubuntu:
  Fix Released
Status in foomatic-filters source package in Karmic:
  Fix Released

Bug description:
  Binary package hint: ghostscript

  My printer doesn't detect for some reason until I restart CUPS, so I
  ran:

  'sudo /etc/init.d/cups restart'. Returned with [OK].

  Then, process 'gs' (Ghostscript?) begins taking up all of my RAM (left
  me at 850/1000mb RAM used, 500/600mb swap used) and my CPU usage goes
  to 100%. Hard drive is chugging hard. I don't know why this is
  happening when I haven't even attempted to print yet.

  I'm not sure if this is a problem with my printer driver or
  Ghostscript (are they the same thing?). I have a Canon i860 printer
  plugged in via USB.

  I'm not sure which log files to add so I'll wait for some comments.
  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/foomatic-filters/+bug/463059/+subscriptions