Munich meeting on 2010-03-20

• Propose requirement with title  'Job Description document should offer a new re-usable structure to define 'scalabletime' requests optionally depending on benchmark results.'

Amsterdam meeting on 2010-04-29

• Source = Draft Spec
• Spreadsheet ID = 115
• Still unclear after 10 mn discussion

Etienne Urbah's position on 2010-04-30

• This requirement reflects a real need, but it is very badly worded.  In fact, it is necessary to split it into 4 separate requirements :
• JD20.1  (Description of the needed functionality)  For 'Wall clock time' and 'CPU time' limits, the Execution Service SHOULD accept Client requirements independently of the speed of the Computing Resource on which the Activity will run
• JD20.2  (Description of the conceptual Client interface)  For 'Wall clock time' and 'CPU time' limits, the Job Description document SHOULD offer a new re-usable structure permitting to describe requirements independently of the speed of the Computing Resource on which the Activity will run
• JD20.3  (First option for a precise description of the Client interface)  For 'Wall clock time' and 'CPU time' limits, the re-usable structure permitting to describe requirements independently of the speed of the computing resource on which the Activity will run SHOULD be the ordered pair (Value, Unit) where :
  - 'Value' is the max number of operations allowed for the Activity,
  - 'Unit' is as unit suitable for a total number of operations, from a closed list to be refined (such as 'Specint2006 * hours' or 'Billions of floating point operations')
  This method is already used by BOINC and has proved it robustness.
• JD20.4  (Second option for a precise description of the Client interface)  For 'Wall clock time' and 'CPU time' limits, the re-usable structure permitting to describe requirements independently of the speed of the computing resource on which the Activity will run SHOULD be a 'scalabletime' specified by a (Value, BenchmarkType, BenchmarkValue) triplet as described in chapter 7.2 of the Specification Draft

Oxana Smirnova's position on 2010-04-30

• This is the real requirement :  *** It must be possible to specify hardware characteristics (e.g. in terms of a benchmark value) corresponding to the indicated performance numbers ***
• And mind it, performance numbers in general are not limited to time.  It might be also memory consumption from another foggy requirement of ours: it obviously will be different on 32- and 64-bit architectures.