<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for that comment ... I had figured out that changing the printer
to the Postscript driver made a HUGE difference. I saw a big decrease
in the overall CPU usage, and the CPU usage would no longer spike at
100% during a print. The pages come out one after another without a
pause. The print job now no longer show up in the
<a class="moz-txt-link-freetext" href="https://127.0.0.1:631">https://127.0.0.1:631</a> print jobs page, as by the time the printer
starts making noise the queue is empty. Now with your description, it
now makes sense why using a PCL printer takes such a huge load on the
system.<br>
<br>
So use Postscript printers with the postscript driver - well worth the
switch<br>
<br>
Joe<br>
<br>
<br>
Michael C Wescott wrote:
<blockquote cite="mid1119114955.1302.34.camel@eriadne" type="cite">
<pre wrap="">On Wed, 2005-06-15 at 07:49, Mike Lichtenwalner wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Joe Guenther wrote:
</pre>
<blockquote type="cite">
<pre wrap="">One of my annoyances with K12LTSP is the extremely slow printing. We
print directly to the IP address of a HP 4000 laserjet with Jet direct
card. It uses CUPS v1.1.22rc1 (K12LTSP 4.2)
The printer waits between each page. The CPU usage (dual 2.4Ghz Xeon)
goes to 100% on both CPUs when printing. When only one job is printing,
one CPU will be on 100% the other lower, but with multiple docs in the
queue (<a class="moz-txt-link-freetext" href="http://127.0.0.1:631">http://127.0.0.1:631</a>) both CPU's peak at 100% ... an the printing
takes a day and an age.
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap="">We also saw that same slow performance when printing to HPLJ 4000 series
printers. The solution was to switch from the recommended Postscript
driver to the "hpijs" driver. More than 90% of our print jobs are text,
and the quality is good (and MUCH faster).
</pre>
</blockquote>
<pre wrap=""><!---->
And one might wonder why.
CUPS is designed to give the same appearance for all printers, at least
to the extent possible. To do this it will, for many printers, convert
the document to be printed to an image. For postscript, this means
taking the postscript and interpreting it and then taking the resulting
image and rasterizing it. The resulting rasterized image is the
converted back to postscript and sent to the printer. The consequences
of all this is a lot of processing and the transformation of documents
into huge postscript images. The images are slow to transfer to the
printer (because of the size) and can be slow to be printed. But they'll
look good, even identical on different brands of printers.
If the printer is described as just a generic postscript printer CUPS
doesn't know about any peculiarities of the printer and so doesn't
bother to convert postscript (from say openoffice) to postscript of
rasterized images and everything is a lot faster. The only downside is
that you lose the ability to invoke some features of the printer like
duplex printing et al. I.e. features that may be peculiar to the type of
printer.
</pre>
</blockquote>
</body>
</html>