perfsonar development work

[Joe Metzger <>]

Vedrin,
It is still a bit early to test the 'Upgraded' ESnet MA.
It is not stable.

I am running FreeBSD on that server. Currently it is a very old version
(4.10) that isn't properly supported by the Tomcat ports package. Tomcat
5.0 installs fine but crashes after a couple of hours. Tomcat 5.5
doesn't install cleanly.

The OS will be upgraded before the end of the week, and this should
streamline a clean re-install of Tomcat, Axis & Exist and hopefully
the resulting server will be more stable.

I have not configured the MA to use the eXist DB yet.

--Joe




Vedrin Jeliazkov wrote:
> Hi,
>
> I've run some simple tests against the upgraded RRD MA at ESnet in an attempt
> to compare its performance against the older release. Here are the timings
> I've got:
>
> 1. One MetadataKeyRequest (summary) [sec]       
> 2. Number of Interfaces (NoI)   
> 3. (NoI x 2) SetupDataRequests (detailed summary) [sec]
> 4. Average SetupDataRequest [msec]
> 5. Average Link latency (RTT) [msec]
> 6. Implementation
>         
>                 (1)     (2)     (3)     (4)     (5)     (6)     
>         
> ESNET           180     415      468     564    202     Java 0.1 (EGEE tag)
> ESNET           296     419     1600    1909    206     perfSONAR-1.0
>
> As you can see, the differences in the number of interfaces and the network
> latency are insignificant, while MetadataKeyRequest's and SetupDataREquest's
> processing time is much longer in the new service version, when compared to
> the older one (multiplied by 1.6 and 3.4 respectively).
>
> If the service is running on the same hardware platform, than we could
> conclude that there is a significant performance loss in the new version,
> which is most probably due to some newly introduced scalability issue. Perhaps
> some more comprehensive tests should be run in order to understand and resolve
> this issue.
>
> Kind regards,
> Vedrin