From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QOS and gameserver lags
Date: Mon, 25 Aug 2003 17:25:39 +0000 [thread overview]
Message-ID: <marc-lartc-106183243905334@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106180852412549@msgid-missing>
On Monday 25 August 2003 12:42, Tom Verbeek wrote:
> Dear list,
>
> I have experimented some time now with HTB queues, and have received
> a lot of help from this list, especially from Stef. Thank you.
>
> My currect Shaper looks like this:
> http://www.designobjekt.de/test/rc.trafficshaper
>
> Unfortunately I still experience lags of this type:
>
> -players from the internet playing on my server feel lags
> -I feel lags when I play on a different server on the internet
>
> How can I find out what are the real reasons for lagging packet
> transport? Maybe its CPU performance of my router, maybe its the
> bandwidth, maybe its my provider...
>
> Any ideas on this will be greatly appreciated!
Can you check the bandwidth used in the different classes? I have a script on
www.docum.org that can do this for you. I ask this because you have
different prio's and you have to be sure you never overlimit a class (send
more then the rate) or the latency can go up.
You also have to check the quantum values. For the 10 kbit class, quantum =
10kbit / 8 (bit -> byte) / 10 (r2q) = 12.5 byte and this < mtu = 1500 byte.
So add quantum 1500 if you create that class.
You can also try to add a fifo qdisc to the classes and not a sfq qdisc.
Especially for the 2:0 qdisc.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-08-25 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 10:42 [LARTC] QOS and gameserver lags Tom Verbeek
2003-08-25 17:25 ` Stef Coene [this message]
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-106183243905334@msgid-missing \
--to=stef.coene@docum.org \
--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.