Log in
Register
Give us Feedback
InviteWorkflow Entry: Make 28 CPUh load on the Grid
| Citations (0) | Version History | Reviews (0) | Comments (1) |
 Version 1
(of 1)
|
Version created on:
25/11/08 @ 14:13:43
by:
Andreas Hoheisel
|
Revision comments 
Last edited on: 17/12/08 @ 14:26:00 by: Andreas Hoheisel
Title: Make 28 CPUh load on the Grid
Type: GWorkflowDL
Preview
(Click on the image to get the full size)
Description
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:-)
Download
Run
Not available
Workflow Components
Not available
Workflow Type
Log in to add Tags
Current:
0.0 / 5
(0 ratings)
Log in to rate and see breakdown of ratings
Statistics
None
Earliest Version:
[1] - Make 28 CPUh load on the Grid
This Workflow only has one version.
Reviews
(0)
Other workflows that use similar services
(0)
There are no workflows in myExperiment that use similar services to this Workflow.
Linked Data
Non-Information Resource URI: http://www.myexperiment.org/workflows/571
Alternative Formats
Copyright © 2007 - 2011 The University of Manchester and University of Southampton
Log in to make a comment
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 ;).