ConsideredURFieldsCPU
Version 1 (Jon Kerr Nilsen, 08/08/2012 05:13 AM)
| 1 | 1 | Jon Kerr Nilsen | h1. List of fields considered for compute accounting |
|---|---|---|---|
| 2 | 1 | Jon Kerr Nilsen | |
| 3 | 1 | Jon Kerr Nilsen | |
| 4 | 1 | Jon Kerr Nilsen | h2. Processors |
| 5 | 1 | Jon Kerr Nilsen | |
| 6 | 1 | Jon Kerr Nilsen | The number of processors used or requested. A processor definition may be dependent on the machine |
| 7 | 1 | Jon Kerr Nilsen | architecture. Typically processor is equivalent to the number of physical CPUs used. For example, if a |
| 8 | 1 | Jon Kerr Nilsen | job uses two cluster “nodes”, each node having 16 CPUs each, the total number of processors would be |
| 9 | 1 | Jon Kerr Nilsen | 32. |
| 10 | 1 | Jon Kerr Nilsen | |
| 11 | 1 | Jon Kerr Nilsen | Example |
| 12 | 1 | Jon Kerr Nilsen | |
| 13 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 14 | 1 | Jon Kerr Nilsen | |
| 15 | 1 | Jon Kerr Nilsen | Ralph: What about cores? Do we need to differentiate between cores and processors? |
| 16 | 1 | Jon Kerr Nilsen | |
| 17 | 1 | Jon Kerr Nilsen | ---- |
| 18 | 1 | Jon Kerr Nilsen | |
| 19 | 1 | Jon Kerr Nilsen | |
| 20 | 1 | Jon Kerr Nilsen | h2. TimeDuration |
| 21 | 1 | Jon Kerr Nilsen | |
| 22 | 1 | Jon Kerr Nilsen | This property identifies any additional measure of time duration associated with the |
| 23 | 1 | Jon Kerr Nilsen | resource consumption. For example, it may report the connection time within a multitasking queue. |
| 24 | 1 | Jon Kerr Nilsen | |
| 25 | 1 | Jon Kerr Nilsen | Example |
| 26 | 1 | Jon Kerr Nilsen | |
| 27 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 28 | 1 | Jon Kerr Nilsen | |
| 29 | 1 | Jon Kerr Nilsen | Ralph: How is it expressed what kind of time duration this property refers to? An attribute? |
| 30 | 1 | Jon Kerr Nilsen | Jon: Wasn't it decided to use StartTime and EndTime instead of TimeDuration? Or is this wall time or CPU time? |
| 31 | 1 | Jon Kerr Nilsen | |
| 32 | 1 | Jon Kerr Nilsen | ---- |
| 33 | 1 | Jon Kerr Nilsen | |
| 34 | 1 | Jon Kerr Nilsen | |
| 35 | 1 | Jon Kerr Nilsen | h2. TimeInstant |
| 36 | 1 | Jon Kerr Nilsen | |
| 37 | 1 | Jon Kerr Nilsen | This property identifies any additionally identified discreet timestamp associated with the |
| 38 | 1 | Jon Kerr Nilsen | resource consumption. For example, it may represent the time the job was queued, rather |
| 39 | 1 | Jon Kerr Nilsen | than the start-time of the job. |
| 40 | 1 | Jon Kerr Nilsen | |
| 41 | 1 | Jon Kerr Nilsen | Example |
| 42 | 1 | Jon Kerr Nilsen | |
| 43 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 44 | 1 | Jon Kerr Nilsen | |
| 45 | 1 | Jon Kerr Nilsen | Ralph: How is it expressed what kind of time this property refers to? An attribute? |
| 46 | 1 | Jon Kerr Nilsen | |
| 47 | 1 | Jon Kerr Nilsen | ---- |
| 48 | 1 | Jon Kerr Nilsen | |
| 49 | 1 | Jon Kerr Nilsen | h2. ALL OK: |
| 50 | 1 | Jon Kerr Nilsen | |
| 51 | 1 | Jon Kerr Nilsen | ---- |
| 52 | 1 | Jon Kerr Nilsen | |
| 53 | 1 | Jon Kerr Nilsen | |
| 54 | 1 | Jon Kerr Nilsen | h2. ComputeUsageBlock |
| 55 | 1 | Jon Kerr Nilsen | |
| 56 | 1 | Jon Kerr Nilsen | This is the block property of the compute usage fields. Similar blocks for storage and other resources should also be added. |
| 57 | 1 | Jon Kerr Nilsen | |
| 58 | 1 | Jon Kerr Nilsen | Example |
| 59 | 1 | Jon Kerr Nilsen | <pre> |
| 60 | 1 | Jon Kerr Nilsen | <ur:ComputeUsageBlock> |
| 61 | 1 | Jon Kerr Nilsen | <!—Compute Record properties go in here --> |
| 62 | 1 | Jon Kerr Nilsen | </ur:ComputeUsageBlock> |
| 63 | 1 | Jon Kerr Nilsen | </pre> |
| 64 | 1 | Jon Kerr Nilsen | |
| 65 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 66 | 1 | Jon Kerr Nilsen | |
| 67 | 1 | Jon Kerr Nilsen | Ralph: ok |
| 68 | 1 | Jon Kerr Nilsen | |
| 69 | 1 | Jon Kerr Nilsen | ---- |
| 70 | 1 | Jon Kerr Nilsen | |
| 71 | 1 | Jon Kerr Nilsen | h2. CpuDuration or ComputeDuration |
| 72 | 1 | Jon Kerr Nilsen | |
| 73 | 1 | Jon Kerr Nilsen | CPU time used, summed over all processes in the job. |
| 74 | 1 | Jon Kerr Nilsen | |
| 75 | 1 | Jon Kerr Nilsen | Example |
| 76 | 1 | Jon Kerr Nilsen | |
| 77 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 78 | 1 | Jon Kerr Nilsen | |
| 79 | 1 | Jon Kerr Nilsen | Ralph: ok |
| 80 | 1 | Jon Kerr Nilsen | |
| 81 | 1 | Jon Kerr Nilsen | ---- |
| 82 | 1 | Jon Kerr Nilsen | |
| 83 | 1 | Jon Kerr Nilsen | |
| 84 | 1 | Jon Kerr Nilsen | h2. StartTime |
| 85 | 1 | Jon Kerr Nilsen | |
| 86 | 1 | Jon Kerr Nilsen | The time at which the usage consumption (i.e. “job”) started. The value of this property |
| 87 | 1 | Jon Kerr Nilsen | may depend on the selected queue system. For example, some systems include time to |
| 88 | 1 | Jon Kerr Nilsen | stage files, others do not. |
| 89 | 1 | Jon Kerr Nilsen | |
| 90 | 1 | Jon Kerr Nilsen | Example |
| 91 | 1 | Jon Kerr Nilsen | |
| 92 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 93 | 1 | Jon Kerr Nilsen | |
| 94 | 1 | Jon Kerr Nilsen | Ralph: ok |
| 95 | 1 | Jon Kerr Nilsen | |
| 96 | 1 | Jon Kerr Nilsen | ---- |
| 97 | 1 | Jon Kerr Nilsen | |
| 98 | 1 | Jon Kerr Nilsen | h2. EndTime |
| 99 | 1 | Jon Kerr Nilsen | |
| 100 | 1 | Jon Kerr Nilsen | The time at which the usage consumption (i.e. “job”) completed. The value of this |
| 101 | 1 | Jon Kerr Nilsen | property may depend on the selected queue system. For example some systems include |
| 102 | 1 | Jon Kerr Nilsen | time to stage files, others do not. |
| 103 | 1 | Jon Kerr Nilsen | |
| 104 | 1 | Jon Kerr Nilsen | Example |
| 105 | 1 | Jon Kerr Nilsen | |
| 106 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 107 | 1 | Jon Kerr Nilsen | |
| 108 | 1 | Jon Kerr Nilsen | Ralph: ok |
| 109 | 1 | Jon Kerr Nilsen | |
| 110 | 1 | Jon Kerr Nilsen | ---- |
| 111 | 1 | Jon Kerr Nilsen | |
| 112 | 1 | Jon Kerr Nilsen | |
| 113 | 1 | Jon Kerr Nilsen | h2. MachineName |
| 114 | 1 | Jon Kerr Nilsen | |
| 115 | 1 | Jon Kerr Nilsen | A descriptive name of the machine on which the job ran. This may be a system hostname, |
| 116 | 1 | Jon Kerr Nilsen | or may be a site’s name for a cluster of machines. The identification of the machine by |
| 117 | 1 | Jon Kerr Nilsen | name may assume the context of the grid in which the machine participates; i.e. machine |
| 118 | 1 | Jon Kerr Nilsen | names may be unique within a specific grid, but do not need to be unique across the set of |
| 119 | 1 | Jon Kerr Nilsen | all grids. |
| 120 | 1 | Jon Kerr Nilsen | |
| 121 | 1 | Jon Kerr Nilsen | Example |
| 122 | 1 | Jon Kerr Nilsen | |
| 123 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 124 | 1 | Jon Kerr Nilsen | |
| 125 | 1 | Jon Kerr Nilsen | Ralph: ok |
| 126 | 1 | Jon Kerr Nilsen | |
| 127 | 1 | Jon Kerr Nilsen | ---- |
| 128 | 1 | Jon Kerr Nilsen | |
| 129 | 1 | Jon Kerr Nilsen | h2. NodeCount |
| 130 | 1 | Jon Kerr Nilsen | |
| 131 | 1 | Jon Kerr Nilsen | Number of nodes used. A node definition may be dependent on the architecture, but |
| 132 | 1 | Jon Kerr Nilsen | typically a node is a physical machine. For example a cluster of 16 physical machines |
| 133 | 1 | Jon Kerr Nilsen | with each machine having one processor each is a 16 “node” machine, each with one |
| 134 | 1 | Jon Kerr Nilsen | “processor”. A 16 processor SMP machine however, is 1 physical node (machine) with |
| 135 | 1 | Jon Kerr Nilsen | 16 processors. |
| 136 | 1 | Jon Kerr Nilsen | |
| 137 | 1 | Jon Kerr Nilsen | Example |
| 138 | 1 | Jon Kerr Nilsen | |
| 139 | 1 | Jon Kerr Nilsen | h3. Comments: |
| 140 | 1 | Jon Kerr Nilsen | |
| 141 | 1 | Jon Kerr Nilsen | Ralph: ok |
| 142 | 1 | Jon Kerr Nilsen | |
| 143 | 1 | Jon Kerr Nilsen | ---- |