about ulpt speed

Wojciech Puchar wojtek at tensor.gdynia.pl
Sat May 7 13:32:54 UTC 2011


>> 
>> Larger postscript files are transmitted longer.
>> 
>> I am not sure but seems it is not printer problem. Any ideas what to 
>> check/change in ulpt?
>
> It's worth trying unlpt.  But if the sending time is proportional to the file

already tried. The only difference is that printer doesn't know when each 
jobs end - so pressing "cancel" on printer by user mean nothing more will 
ever print after that ;) - as cancel works by ignoring data until end of 
job.

speed is same.

> size, it's probably not that.

Yes it's not that. i tried making dumb 200MB postscript file and pressed 
cancel just after starting sending data. so printer just had to receive 
and ignore data - got 2.5MB/s with
cat file >/dev/ulpt0

tried

dd if=file of=/dev/ulpt0 bs=1m - same speed.

in actual printouts it's more like 200kB/s or less.

It may be printer's problem but not it's postscript processor

Kyocera FS-3920DN have identical CPU and identical amount of RAM and 
handles printouts by LAN at 100Mbit/s speed even on complex postscript 
files.

Do you have any idea what to check more ?



More information about the freebsd-questions mailing list