GRAM5 tests

This page is meant to contain the information we gather while testing GRAM5.

GRAM5 validation tests

Jeff and Igor did a first round of tests to check if GRAM5 (alpha2) indeed worked and how it compared to GT2 on a small scale.

• gram5basetest.pdf: GRAM5 validation test

GRAM 5 benchmarking

GRAM5 alpha2 was installed on osg-gw-5.t2.ucsd.edu.

• File transfer is not working properly. All further tests are without input or output files.
• Submitting from a machine on a local LAN, 1Hz (50 jobs/min) job turnaround is easy to acchieve. Peaks of 3Hz (170 jobs/min) has also been observed.
  If monitoring is not needed, 3Hz (200 jobs/min) sustained rate should be acchievable.
  For more details: rates_gt5a2_ucsd.pdf
• Submitting from a machine on the other side of the world, the job turnaround is about 17 jobs/min. Peaks of 30 jobs/min has also been observed.
  If monitoring is not needed, 200 jobs/min (3Hz) sustained rate should be acchievable.
  For more details: rates_gt5a2_ucsd_r2.pdf
  Note: No clear conclusions, yet... I have found that GRAM5 gets slower in time, so the results may be affected by that.

GRAM 5 beta 1

Installation

While up to alpha3, GRAM5 played well on top of a previous installation of a 1.10.1 VDT, beta1 needs some changes:

• The initial install used the VDT perl, and this created some problems. Make sure you use the system perl.
  Configured in globus.v5b1/libexec/globus-sh-tools-vars.sh
• jobmanager-fork is not the default anymore; one needs to change the symlink in globus/etc/grid-services

More changes:

• copied VDT $GLOBUS_LOCATION/etc/gridftp.cong
• created $GLOBUS_LOCATION/var/log (used by gridFTP)

OSG jobmanager-condor

OSG uses a patched/augmented version jobmanager-condor (condor.in->condor.pm). The jobmanager-condor changed slightly between GT2 and GRAM5, so we had to merge the two.

The work was performed by Christopher Theissen, and is documented at here.

-- IgorSfiligoi - 2009/08/12