Skip to Content.
Sympa Menu

perfsonar-dev - Re: performances parameters [Was: Re: List of services to include in perfSONAR-2.0]

Subject: perfsonar development work

List archive

Re: performances parameters [Was: Re: List of services to include in perfSONAR-2.0]


Chronological Thread 
  • From: Joe Metzger <>
  • To: Nicolas Simar <>
  • Cc: "Jeff W. Boote" <>, Loukik Kudarimoti <>, Szymon Trocha <>, Andreas Hanemann <>, Jerome Durand <>, Luis Marta <>, 'Eric Boyd' <>, 'Martin Swany' <>, 'Roman Lapacz' <>, 'Vedrin Jeliazkov' <>, 'Verena Venus' <>,
  • Subject: Re: performances parameters [Was: Re: List of services to include in perfSONAR-2.0]
  • Date: Fri, 07 Jul 2006 09:47:14 -0500

Nicolas,
I like the direction your headed, but I am not so sure about your
initial assumptions.

The ESnet SNMP collection system is currently collecting 4622
targets when you add up all the traffic, error, discard and qos
specific interface counters. All of these will be rolled into
perfSONAR server(s) once AAA is available...

Is it reasonable to multiple your numbers by 5? :-)

--Joe


Nicolas Simar wrote:


Jeff W. Boote wrote:

Other:
- performance targets (we need to quantify, but it would be good to

During a previous conf call internal to JRA1, we had some thoughts on performances parameters (based on TNO feedback).
This is specific for an MA having interface statistics.

The largest network we have encountered so far is Uninett with 700 interfaces. So a target of 1000 interfaces is something we should achieve.


We could have several metrics per service:
- link utilisation in/out (2)
- interface input errors (1)
- interface drops and per service (BE, LBE, Premium, NC) (4)
That makes 7 values.

A visualisation tool like a weathermap displaying those data would every 5 minutes querry the MA for all those data.
This makes 7000 requests over 5 minutes - 300 secs (Assuming that the requests are evenly spread, which is not the case). This means 24 request per seconds.

One could think that several tools may be querying simultaneously the MA, let's say 3. This would mean 72 requests per seconds.

We could also assume that before sending those requests, the client would want to know all the interfaces and metrics made available by the MA: so this means three MetadataKeyRequest every 5 minutes (unless it uses the LS for that).

Those figures are I think long term goals. When a large infrastructure would be deployed.

I don't have any idea on how to estimate the number of request done to the LS or to the

My 2 cents,




Archive powered by MHonArc 2.6.16.

Top of Page