All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwidth Control Tolerances
Date: Tue, 06 Jan 2004 17:20:46 +0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0401061053030.6395@gargoyle.wi.securepipe.com> (raw)
In-Reply-To: <002801c3d3eb$4634da30$6401a8c0@pturley>

Hello Patrick,

Please excuse my suggestion if you have already considered the issue I
indicate below from Stef's FAQ.

 : I have measured the performance of HTB with iperf and found it to be
 : very close to expected (i.e., within 5%). I have a colleague who is
 : measuring the performance by ftp'ing large files and recording the time
 : required to make the transfer. He is seeing an average throughput that
 : is nearly 10% away from the theoretical, with occasional excursions to
 : nearly 30%.

How have you defined your PSCHED_CLOCK_SOURCE?  See this URL:

  http://www.docum.org/stef.coene/qos/faq/cache/40.html

 : My colleague is now questioning the quality of the traffic control
 : algorithms and wondering two things:

Let's be careful with the baby and the bathwater.  The algorithms have
been vetted.  The implementation may not be ideal, but implementations
always suffer from compromises, right?

 : 1) What tolerance can we guarantee and advertise?

Measure the deviations from your specified bandwidth after changing your
setting for PSCHED_CLOCK_SOURCE.  Advertise your measured tolerance
accordingly.

 : 2) Can the tolerance be improved, since the values he has measured are
 : unacceptable?

I don't know--see the above link, and check how your kernel was compiled.
Others on this list may have further suggestions for you.

Good luck,

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2004-01-06 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06  0:23 [LARTC] Bandwidth Control Tolerances Patrick Turley
2004-01-06 17:20 ` Martin A. Brown [this message]
2004-01-06 18:02 ` Patrick Turley
2004-01-06 18:02 ` Patrick Turley
2004-01-06 18:03 ` Patrick Turley
2004-01-07 17:36 ` 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=Pine.LNX.4.58.0401061053030.6395@gargoyle.wi.securepipe.com \
    --to=mabrown-lartc@securepipe.com \
    --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.