Re: printing dead slow since squeeze

[hobbes@poukram.net (Rémi Letot)]

Camaleón <noelamac@gmail.com> writes:

> On Fri, 02 Mar 2012 17:05:10 +0100, Rémi Letot wrote:
>
>> I just updated a bunch of servers from etch to squeeze (yes I know, took
>> my time :-)
>
> And I still worried because I have to keep lenny... :-P

lol :-)

>
> Did you run an in-place update or did you install squeeze from
> scratch?

in-place update, and I had to ressort to the equivallent of a software
chainsaw several times to make it work :-)

>> Everything works fine after a bit of tweaking, except printing. I have a
>> networked postscript printer managed through cups, and since the upgrade
>> it has been dead slow.
>
> (...)
>
> Okay, as a first round I would try to debug if the origin of the slowness 
> is related to the network connection.

I don't think so, my network has no problem otherwise. Besides, the file
that I print is very small. It's only one page, some KB. The number of
pages comes from using lp -n .

> Is printing pain slow when printing from the local host (the computer 
> that is connected to the printer) or you note some difference in the 
> processing speed when sending the job locally?

I have no locally connected computer, it's only a network printer. So no
easy way to test this.

> And just in case, if the printer supports it, I would test with a PCL6 
> driver, it would be interesting to see the results to compare.

Will try that tomorrow.

> Also, the more information you provide for the printer (brand name, 
> model, connection type, ppd file in use...), the better.

Brother HL-4050CDN, network connection, ipp protocol, ps filter.

The ppd is the one provided with cups, and I also tried with the
generic ps ppd.

I force reinstalled the whole cups stack (cups and co, foomatic,...)
just to be sure that no etch file was lying around, but it didn't help. 

Thanks,
-- 
Rémi