perfsonar development work

["Vedrin Jeliazkov" <>]

Hi Guilherme,

Guilherme Rhoden 
<>
 wrote:

> Hi all,
> 
> I've tried to deploy a java MA-RRD (snapshot 20060901) with 413
> interfaces. The service is very very slow when I tried to get all the
> metadata's of the defined interfaces with perfSONAR-UI.

Did you configure the service to use eXist database as a storage for the RRD
XML config? In case you have, did you configure the RRD MA service to access
eXist via http, rather than via xmlrpc?

If you haven't done the later or both of the above, please consider them.
There's some performance gain with such settings, especially when you have a
large RRD XML config, as in your case.

> The XML configuration file has 1,4Mb and the java process is using more
> that 330Mb of memory.
> 
> Anyone has some experience with this number of interfaces?

There are so many contributing factors, that it would be rather difficult to
make comparisons. Here at ISTF we were forced to reduce the number of
interfaces in our config, because of performance issues. But, our server has a
very limited amount of RAM (768 MB) and hosts LS and RRD-MA-Python in addition
to RRD-MA-Java. We found helpful the following JVM options in our particular
case:

-Xms192m -Xmx192m -Xincgc

The options select a different (incremental) garbage collector than the
default one and also make its work easier by setting the initial and maximum
heap size to the same value.

> The ESNET has 419 interfaces but perfSONAR-UI can't contact this MA.

You probably have an old version of MA.conf in your perfsonarUI installation.
It should work if you update ESNET's line as follows:

ESNET,http://mea1.es.net:8080/axis/services/MeasurementArchiveService,NMWG2v2_netutil,"",utilization,utilization

The most recent version of MA.conf is available on the wiki as a separate
file:

http://wiki.perfsonar.net/jra1-wiki/index.php/PerfsonarUI

Kind regards,
Vedrin