From: Tom Verbeek <tom@designobjekt.de>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] ensure game server latency
Date: Tue, 05 Aug 2003 18:51:38 +0000 [thread overview]
Message-ID: <marc-lartc-106011188400720@msgid-missing> (raw)
AK> You need to shape in both directions... so, if you don't
AK> guarantee the server some download bandwith, you'll encounter
AK> lags pretty much all the time.
I thought I could only shape upload traffic??
BTW: download bandwidth is not the issue: I've got an ADSL connection
of 2MBit/s down and 192Kbit/s up.
>> I can post my script if there is an interest in it...
AK> You should definitely put it somewhere so that people
AK> can have a look at it.
Its here now:
http://www.designobjekt.de/test/rc.trafficshaper
Any comments strongly appreciated!
Thanks,
Tom.
--
Word Perfect isn't, Excel doesn't, Works won't.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-08-05 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 18:51 Tom Verbeek [this message]
2003-08-05 19:28 ` Re[2]: [LARTC] ensure game server latency Stef Coene
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=marc-lartc-106011188400720@msgid-missing \
--to=tom@designobjekt.de \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.