[mrtg-developers] Calculating 95th percentile

[Westlake, Simon]

Thanks for the info Alex, I will give it a shot. Sorry for posting to
the wrong list! 


--
Simon Westlake
Time Warner Cable Business Class
Network Engineer
Ph: 414.908.4791 | Cell: 414.688.7956
-----Original Message-----
From: mrtg-developers-bounces at lists.oetiker.ch
[mailto:mrtg-developers-bounces at lists.oetiker.ch] On Behalf Of Alex van
den Bogaerdt
Sent: Thursday, October 11, 2007 11:15 AM
To: mrtg-developers at lists.oetiker.ch
Subject: Re: [mrtg-developers] Calculating 95th percentile

On Thu, Oct 11, 2007 at 11:59:48AM -0400, Westlake, Simon wrote:

> As a short introduction, the code you provided works great for drawing
a
> line at 95% of the max value. If I can find a way to do what I need
this
> simply, it will make my life a lot easier.

It does not, at least not when I wrote that code.

> However, what I need to calculate is 95th percentile in billing terms
> (see http://en.wikipedia.org/wiki/Burstable_billing). The problem with
> the vdef 95 percent method is that if there is any time a user bursts
to
> 100 megs, it will calculate the 95th percentile as 95 megs. The
> universally accepted method (from a billing perspective) of
calculating
> 95th percentile is to take all your samples (typically 1 every 5
> minutes), sort them from smallest to largest, discard the top 5% and
> then bill at the largest value. By this method, if a user had burst to
> 100 megs 4.9% of the month and had maxed at 12 megs the rest of the
> month, the 95th percentile would be calculated as 12 megs. Quite a big
> difference..

Using somewhat old code, which may have changed since then:

- sort:   NaN < -INF < finite_values < INF

This gives you sorted rates:
                qsort(array,step,sizeof(double),vdef_percent_compar);

This computes the Xth percentile position:
                field = (steps-1)*dst->vf.param/100;
This takes the rate from that position:
                dst->vf.val  = array[field];

I don't know why you think the percentile function is just shorthand
for "*95/100". It really is not.

> Before I go too far in figuring out the problem with my fetch
statement,
> is there some reasonable way of doing this simply with RRDTool that I
> should investigate, or for a calculation of this complexity, will I
need
> to do the calculation via some other means? Looking at the RRDTool
> documentation, I don't really see an easy way to do this.

Investigate what happens in the scenario you talk about. Update with
all zeros, except one update which should be 100M. Then look what value
is reported back.

Alex
P.S.  What is this doing on mrtg-developers, while it should clearly
be on rrdtool-users ?

_______________________________________________
mrtg-developers mailing list
mrtg-developers at lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg-developers
This E-mail and any of its attachments may contain Time Warner
Cable proprietary information, which is privileged, confidential,
or subject to copyright belonging to Time Warner Cable. This E-mail
is intended solely for the use of the individual or entity to which
it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents
of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any
copy of this E-mail and any printout.