CCSINTEGRATING COMPUTING RESOURCES
ON MULTIPLE GRID-ENABLED
JOB SCHEDULING SYSTEMS
THROUGH A GRID RPC SYSTEM
Yoshihiro Nakajima
Advisor: Mitsuhisa Sato
University of Tsukuba

2007/10/30

1Motivation
2

Need for High Throughput Computing(cf. Simulations for drug design, Circuit design…)
 Many kinds of Grid-enabled Job Scheduling System(GJSS) have been developed XtremWeb, Condor, Grid engine, CyberGRIP, GridMP…

User wants to use massive computing resources ondifferent sites easily
 Different management policy and middleware on eachsites User should write extra code to adapt environment User does not want to stop calculation by system faults(Needs for transparent Fault-tolerance mechanism)

Provide RPC style programming model on GJSS

3Background: OmniRPC as an exampleof Grid RPC system
Provide seamless parallel programming for local cluster tomulti-cluster in a grid environment
Make use of remote PC clusters as Grid computing resources
OmniRPC consists of three kinds of components:
Client, Remote executable, AgentOmniRPC agent works as a proxy of the communication
between client program and remote executables
Agent invocation
communication

ClientInternet/
Network

Multiplex I/O

Agentrex rexrex

Rex: Remote
ExecutableObjective and Design of Grid RPC system
for integrating computing resources on GJSS
ObjectivePC Cluster

OmniRPC
Remoteexecutable

Provides unified and parallel programming model by RPC on GJSS
OmniRPC
Client Program

Provide Fault-tolerant features for Grid RPC systemon the worker programs

Exploit massive computing resources on different sites simultaneously

XtremWeb
Dispatcher

Client PC

Design of proposed system
Decoupling computations and data transmission
from RPC mechanismDesign the agent mechanism to bridge between
Grid RPC and GJSS

Using document-based communication,rather than connection-based communicationAPIs to adopt different GJSS’s

CyberGRIPSRMDCondor Pool
CyberGRIP
GRM

Overview of the proposed system
Model of OmniRPC on a GJSS

The proposed system canSubmit a RPC computation as a job to GJSS

Guarantee transparent fault-tolerant execution
on the side of worker programs

Volunteer PCs

4

Implementation and Performance
evaluation of the Proposed system
Elapsed time in case of issuing 128 PRCs
(240 sec per RPC) in parallel with 16 nodes[ideal elapsed time takes 1920 sec]

 Condor (U of Wisconsin)->OmniRPC/C
 Grid Engine (SUN) -> OmniRPC/GE XtremWeb (INRIA) -> OmniRPC/XW CyberGrip (Fujitsu lab) ->OmniRPC/CG

OmniRPC/XW
OmniRPC/GE

Elapsed Time (s)We have implemented the system toexploit 4 major grid job schedulers

The proposed system archives almost
the same performance of original
OmniRPC

OmniRPC/CG
OmniRPC

2500
2000
1500
10005000OmniRPC/C

110 100 100010000Data transfer size / RPC (KB)
Stop condor
daemon on
4 nodes OmniRPC/{XW,CG,C,GE} have small

Kill thecondor
processes on
2 nodesStart the another jobs
to disturb the condor
jobs on 4 nodes

Reboot 7 nodes
without the server

16

Fault-tolerance facility of the
proposed system works well and user
can take advantage of the facility

14
Number of Running Jobs

performance degradation (10% lower)
compared with original OmniRPC

12
10864
200200400600800 1000 1200 1400 1600 1800 2000 2200 2400
Elapsed Time (s)# of running jobs when injecting artificial
5 faults

Discussion:
Pros and Cons of the proposed system
Pros
OmniRPC/{XW,CG,C,GE} can use large-computing
resource pools managed by GJSSs on different sites.
OmniRPC/{XW,CG,C,GE} can take advantage of faulttolerant facility in worker program’s sideThe original OmniRPC does not support FTConsPerformance of the OmniRPC/{XW,CG,C,GE} might belower than that of the original OmniRPC If the computation time of a RPC takes longer (more than 10min), performance degradation will be negligible
6Summery and Future Works
7

We have proposed a framework for a parallel programming modelby RPC for integrating large-scale computing resource pools byGJSSs
Agent bridging RPC and job scheduling system by converting connectionbased communication to document-based communication

We have implemented the system as an extension of the OmniRPC
system on XtremWeb, CyberGRIP, Condor and Open Source Grid
EngineAchieve as approximately same performance as that of original OmniRPC Can takes advantage of FT in worker program side

Future Works
Apply to another GJSS Dynamic RPC scheduling by using computing usage information in each site