From: Corey <corey@bitworthy.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] "laggy" drawterm on local network?
Date: Sat, 15 May 2010 14:31:57 -0700 [thread overview]
Message-ID: <201005151431.57917.corey@bitworthy.net> (raw)
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. For instance, mousing up/down
the rio menus, and drawing/moving new rio windows, scrolling through large
amounts of text... all produce regular finegrained intermittent delays before
"catching up"... it's just past the threshold of annoying/frustrating -
especially as I was expecting smother operation here on my lan over
relatively decent bandwidth.
Before possibly spinning my wheels attempting to fix/diagonse potential
issues on my home network/routing - I'd like to ask: is this actually normal,
or is it likely something's up w/ my network to cause such noticeable lag on
drawterm? (I've at least done the obvious to ensure no other network traffic
is saturating my lan's pipe)
Thanks!
next reply other threads:[~2010-05-15 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 21:31 Corey [this message]
2010-05-15 21:33 ` Corey
2010-05-15 23:49 ` erik quanstrom
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=201005151431.57917.corey@bitworthy.net \
--to=corey@bitworthy.net \
--cc=9fans@9fans.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).