That works wonderfully! I've only done basic testing with "yes $(seq 1 1000)". The highest value I found where the response to ctrl-c was instant was
#define BYTES_MAX 100000 That happens to be about the total on-screen characters of my terminal times 5. If it was me, I'd set it to that or some similar multiple at run time. I'll see about testing interactive use shortly, with that 100000 number. -Robin On Tue, Dec 20, 2011 at 07:21:49AM +0000, Nicholas Marriott wrote: > Ok ssh changes the game quite a lot. Can you try the diff I sent > and see if that helps and if so what value for BYTES_MAX is > acceptable? > > If it doesn't help let me know, I have another diff to rate limit > outgoing data that might help instead. Or if not that, there is > other stuff we can try. > > > On Mon, Dec 19, 2011 at 04:47:12PM -0800, Robin Lee Powell wrote: > > On Tue, Dec 20, 2011 at 12:04:28AM +0000, Nicholas Marriott wrote: > > > On Mon, Dec 19, 2011 at 03:59:39PM -0800, Robin Lee Powell wrote: > > > > I've never had this level of problem with screen, at all, and I > > > > used it for many many years for everything. > > > > > > > > On Mon, Dec 19, 2011 at 11:43:04PM +0000, Nicholas Marriott > > > > wrote: > > > > > screen does not successfully rate limit either or if it does > > > > > nobody has yet to clearly demonstrate a case where it does. > > > > > It's response times for running eg "yes" and hitting ^C or > > > > > creating a new window are roughly the same as tmux, give or > > > > > take a few seconds. > > > > > > > > 0____o > > > > > > > > We're seeing *very* different behaviour, then. > > > > > > > > In a bare terminal or in a fresh screen, after running "yes" for > > > > 30 seconds, I get my prompt back as close to instantly as makes > > > > no difference. > > > > > > > > In tmux it takes 8 seconds. > > > > > > For me it takes 3-5 seconds for both and always has... > > > > Huh. > > > > > What terminal are you using? What size is it? What platform? > > > > > > Are you using tmux remotely? > > > > As I mentioned, I'm running PuTTY on Windows, sshing out to a Linux > > box in the same house (over wifi). > > > > TERM before I run screen is "xterm". TERM in screen is "screen". > > TERM in tmux is "screen". > > > > In all cases it's 132 wide and 85 high. > > > > -Robin > > > > -- > > http://singinst.org/ : Our last, best hope for a fantastic future. > > Lojban (http://www.lojban.org/): The language in which "this parrot > > is dead" is "ti poi spitaki cu morsi", but "this sentence is false" > > is "na nei". My personal page: http://www.digitalkingdom.org/rlp/ > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users > -- http://singinst.org/ : Our last, best hope for a fantastic future. Lojban (http://www.lojban.org/): The language in which "this parrot is dead" is "ti poi spitaki cu morsi", but "this sentence is false" is "na nei". My personal page: http://www.digitalkingdom.org/rlp/ ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
