From owner-freebsd-questions@FreeBSD.ORG Sat May 7 13:32:54 2011 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF6AD106566C for ; Sat, 7 May 2011 13:32:54 +0000 (UTC) (envelope-from wojtek@tensor.gdynia.pl) Received: from tensor.gdynia.pl (tensor.gdynia.pl [89.206.35.72]) by mx1.freebsd.org (Postfix) with ESMTP id 33E538FC13 for ; Sat, 7 May 2011 13:32:53 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by tensor.gdynia.pl (8.14.4/8.14.4) with ESMTP id p47DWpWT015561; Sat, 7 May 2011 15:32:51 +0200 (CEST) (envelope-from wojtek@tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.4/8.14.4) with ESMTP id p47DWoiw001480; Sat, 7 May 2011 15:32:50 +0200 (CEST) (envelope-from wojtek@tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.4/8.14.4/Submit) with ESMTP id p47DWnr5001477; Sat, 7 May 2011 15:32:49 +0200 (CEST) (envelope-from wojtek@tensor.gdynia.pl) X-Authentication-Warning: wojtek.tensor.gdynia.pl: wojtek owned process doing -bs Date: Sat, 7 May 2011 15:32:49 +0200 (CEST) From: Wojciech Puchar To: Warren Block In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (tensor.gdynia.pl [89.206.35.72]); Sat, 07 May 2011 15:32:51 +0200 (CEST) Cc: questions@freebsd.org Subject: Re: about ulpt speed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2011 13:32:54 -0000 >> >> 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 ?