Bandwidth-Aware Scheduling of Workflow Application on Multiple Grid Sites

Listing 2

Parts of the  .dax file for the test workflow having 10 tasks, emphasizing how each task of workflow is created using pegasus-keg command and the structure of the overall workflow showing dependencies among the tasks.

⋯

<job id=“j9” namespace=“test-10” name=“J” version=“4.0”>

 <argument>-a J -T 94 -i <file name=“data.gj”/> <file name=“data.hj”/>  <file

name=“data.ij”/> -G 1000000 -o <file name=“data.j”/> </argument>

 <profile namespace=“pegasus” key=“runtime”>94</profile>

 <uses name=“data.gj” link=“input” transfer=“false” register=“false” size=“4345853”/>

 <uses name=“data.hj” link=“input” transfer=“false” register=“false” size=“3618930”/>

 <uses name=“data.ij” link=“input” transfer=“false” register=“false” size=“4172567”/>

 <uses name=“data.j” link=“output” transfer=“true” register=“true” size=“1000000”/>

</job>

⋯

 <child ref=“j1”>

  <parent ref=“j0”/>

 </child>

 <child ref=“j2”>

  <parent ref=“j0”/>

 </child>

 <child ref=“j3”>

  <parent ref=“j0”/>

 </child>

 <child ref=“j4”>

  <parent ref=“j0”/>

 </child>

 <child ref=“j5”>

  <parent ref=“j0”/>

 </child>

 <child ref=“j6”>

  <parent ref=“j2”/>

 </child>

 <child ref=“j7”>

  <parent ref=“j1”/>

  <parent ref=“j3”/>

  <parent ref=“j5”/>

 </child>

 <child ref=“j8”>

  <parent ref=“j1”/>

  <parent ref=“j3”/>

  <parent ref=“j4”/>

 </child>

 <child ref=“j9”>

  <parent ref=“j6”/>

  <parent ref=“j7”/>

  <parent ref=“j8”/>

 </child>

</adag>