Make 28 CPUh load on the Grid

Created: 2008-11-25 14:13:43      Last updated: 2008-12-17 14:25:59

This workflow makes 28 CPU hours load on a Grid. Therefore it calls 100 times (represented by 100 input tokens) the program "makeload", which makes 1000 Seconds load each. The processing is done recurrent, so you can use this workflow to benchmark the speedup of your Grid environment, or just to heat up your computer center...

This workflow also serves as an example of a typical parameter study modeled with GWorkflowDL.

Of cause this workflow can only be invoked with a X509 certificate (Grid proxy) which is valid in the target Computing Grid. We do not want everybody to heat up our computer center:-)

 

Information Preview

Medium

Information Run

Not available


Information Workflow Components

Not available

Information Workflow Type

GWorkflowDL

Information Uploader

Information License

All versions of this Workflow are licensed under:

Information Version 1 (of 1)

Information Credits (1)

(People/Groups)

Information Attributions (0)

(Workflows/Files)

None

Information Tags (9)

Log in to add Tags

Information Shared with Groups (2)

Information Featured In Packs (0)

None

Log in to add to one of your Packs

Information Attributed By (0)

(Workflows/Files)

None

Information Favourited By (0)

No one

Information Statistics

 

Citations (0)

None


Version History

In chronological order:



Reviews Reviews (0)

No reviews yet

Be the first to review!



Comments Comments (1)

Log in to make a comment

  • Thursday 24 September 2009 17:40:22 (UTC)

    Hello Andreas. Looking through various resources here on this site I found your workflows. Then I spotted a typo in the description of this one ("Of cause" -> "Of course" ?). Then I thought - well, perhaps it's a good opportunity to test if myExperiment is really that open - so I entered here and I tried to find an "edit" button to correct the typo.

    Well, as you see I haven't found any so you need to correct it yourself ;).




Workflow Other workflows that use similar services (0)

There are no workflows in myExperiment that use similar services to this Workflow.