Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Re: [GN2-JRA1] [Ticket#2007103110000016] Problem with SWITCH RRD MA

Subject: perfsonar development work

List archive

Re: [pS-dev] Re: [GN2-JRA1] [Ticket#2007103110000016] Problem with SWITCH RRD MA


Chronological Thread 
  • From: Roman Lapacz <>
  • To:
  • Cc: Nina Jeliazkova <>, GN-JRA1-list <>, "" <>
  • Subject: Re: [pS-dev] Re: [GN2-JRA1] [Ticket#2007103110000016] Problem with SWITCH RRD MA
  • Date: Tue, 04 Dec 2007 14:08:15 +0100

Jason Zurawski wrote:
Nina;


Bumping to this to pS-Dev, since this is something interesting to mention...

strangely enough, after restarting PerfsonarUI and changing nothing
else, it seems to be working.
It is even reasonably fast, UNLESS:

if you at any time select "retrieve all" it will remain slow for a
loooooooong time after that, even if you issue a stop.
I installed a service with your metadata config file. My local machine
is 2.0 GHz with 512 MB memory and getting all metadatas took about 50
secs (I was using simple java command-line app).
Perfsonar UI "Retrieve all" sends not only a single metadata request,
but after it a number of setupdata requests in order to retrieve some
statistics. In case of SWITCH MA with 343 interfaces, this results in
sending 43 SetupData requests simultaneously (according to the default
settings). These set of requests might be the reason of server being
fully loaded.
I think the "retrieve all" is a good thing to have, but particularly
when testing large deployments (ESnet has 1000s of interfaces for
example) it would be good to have functionality to do the metadata
request to populate pS-UI, then selectively retrieve interface info for
data requests instead of automatically getting everythihng. Working on
a Mac mini at SC, it was impossible to run pS-UI due to the volume of
data generated by certain services (also caused repeated Heap Overflows).
I agree for testing purposes it will be convenient to send obnly
metadata request. I am thinking of two options
1) add a new menu item (in addition to retrieve all) with
functionality to send only metadata request , therefore the table will
be filled in only with interface metadata and no utilization
statistics, and no data will be displayed at barchart /radar chart. In
this case, could you suggest an appropriate title for the new menu item?
or
2)add an option somewhere in order to switch the behaviour of
"Retrieve All" between current behaviour and sending only metadata
request.

Which will be the preferred way?

Option 1 makes the most sense to me, I would call this choice "Populate"
or something similar. After this step there would need to be two
options for data retrieval: the current "retrieve all", then the ability
to select interfaces from the table, and simply "retrieve selected".
Anyone else feel strongly one way or another about this?

I agree with you. It's reasonable proposal.

Roman

-jason





Archive powered by MHonArc 2.6.16.

Top of Page