perfsonar development work

[Nina Jeliazkova <>]

Jason,

Jason Zurawski написа:

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?

Regards,
Nina

An usefull performance test will be to send several tens of requests
simultaneously from a simple command line (or SOAPUI) client .

Stop doesn't stop connections (there is no way in Axis1 to interrupt
connection), it just tells the client side not to wait for them.
  
    

Just a suggestion, stop is probably a poor word to use (I realized how
it worked before, but newer users may not understand the distinction). 
I would expect 'abort' to do the behavior you have described. 

-jason
  

-- 
---------------------------------
Dr. Nina Nikolova-Jeliazkova
Institute for Parallel Processing
Bulgarian Academy of Sciences
Acad. G. Bonchev St 25-A
1113 Sofia, Bulgaria
Tel: +359 886 802011
ICQ: 10705013
www: http://ambit.acad.bg/nina
---------------------------------
PGP Public Key
http://cert.acad.bg/pgp-keys/keys/nina-nikolova-0xEEABA669.asc
	8E99 8BAD D804 1A43 27B7  7F87 CF04 C7D1 EEAB A669
---------------------------------------------------------------