From: erik quanstrom <quanstro@quanstro.net>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] "laggy" drawterm on local network?
Date: Sat, 15 May 2010 19:49:32 -0400 [thread overview]
Message-ID: <a7d1b1e1beab8b35f50b0ae0d0e43b9a@kw.quanstro.net> (raw)
In-Reply-To: <201005151433.54884.corey@bitworthy.net>
On Sat May 15 17:33:49 EDT 2010, corey@bitworthy.net wrote:
> On Saturday 15 May 2010 2:31:57 Corey wrote:
> > I'm on a 802.11g here on my lan in my house, where my cpu/auth server
> > sits - and drawterm is noticeably slow/laggy.
> <snip>
>
> Oh yeah - I'm using tcp and not il.
clearly! /dev/draw is very efficient, but graphics are being
pushed over the wire. and since tcp is not record preserving,
a local wireless network is just the sort of thing where the
delayed ack might hurt.
i use wireless (borrowed laptop) about once a month and
don't see any issues. perhaps you're on a busy or contended
channel?
- erik
next prev parent reply other threads:[~2010-05-15 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 21:31 Corey
2010-05-15 21:33 ` Corey
2010-05-15 23:49 ` erik quanstrom [this message]
2010-05-16 1:10 ` Corey
2010-05-16 1:26 ` erik quanstrom
2010-05-16 1:35 ` Corey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7d1b1e1beab8b35f50b0ae0d0e43b9a@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).