All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] API using cbq / tc ?
Date: Wed, 12 Feb 2003 17:45:15 +0000	[thread overview]
Message-ID: <marc-lartc-104507205921901@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104453716713244@msgid-missing>

On Wednesday 12 February 2003 09:29, devik wrote:
> > > So if you use 5s interval in rrd it seems ok for me (it
> > > is what i plan to do here).
> >
> > If you receive an update each second, you have the feeling it's realtime.
> > It's slow enough to understand the data and it's fast enough to feel it
> > as real-time.  It's also fast enought that you get new data before you
> > are tired to look at the old data.
>
> hmm :) really depends on angle of view .. From my experience
> ("btw" tool) 1sec is too fast because I see results like:
> 30kbit, 28, 10, 33,15,35 .... I can see every packet burst
> and thus my brain is not good enough to compute average from it
> on fly. So I use 10sec moving average to have something senseful.
>
> On other side, there are two time variables :
> - show rate
> - EWMA time constant
>
> I agree that you can have time constant 30sec and
> sampling/show rate 1sec. Then you get smooth and fast
> updates :)
> Still you can use rrd because it is hierarchical - you
> can have last minute in secs resolution, then last hour
> in minutes resolution etc...
Storing the value is no problem, but showing.  If don't think it's such a good 
idea to refresh a webpage and relaod (and draw) the graphs on it each second.  
So rrd for long term overview, java (of VB) for real time overview.

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/

  parent reply	other threads:[~2003-02-12 17:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:20 [LARTC] API using cbq / tc ? Srikanth
2003-02-07  2:28 ` S Mohan
2003-02-07  4:37 ` Srikanth
2003-02-07  7:44 ` Stef Coene
2003-02-08  7:02 ` Ming-Ching Tiew
2003-02-08 10:39 ` Stef Coene
2003-02-08 13:04 ` Ming-Ching Tiew
2003-02-08 13:22 ` Stef Coene
2003-02-09  3:45 ` Ming-Ching Tiew
2003-02-09  7:26 ` Henry Yen
2003-02-09 13:39 ` Stef Coene
2003-02-10  1:58 ` mingching.tiew
2003-02-10  8:59 ` Stef Coene
2003-02-10 18:01 ` Jay Wineinger
2003-02-10 18:20 ` Stef Coene
2003-02-11 16:59 ` Martin Devera
2003-02-11 18:16 ` Stef Coene
2003-02-12  8:29 ` devik
2003-02-12 17:45 ` Stef Coene [this message]
2003-02-13  8:30 ` devik
2003-02-13 10:36 ` mingching.tiew
2003-02-13 18:39 ` Stef Coene
2003-02-13 18:40 ` Stef Coene
2003-02-14  3:58 ` mingching.tiew

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-104507205921901@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.