Hi Daniela,
Re: Would it be possible to use memory/thread (i.e. available per job
slot) ?
I hope you don't mind me saying so, but this might be a bother. You see,
some sites give various HEPSPEC06 readings for the exact same hardware.
They select a number of job slots at various values between (say) cores
and cores*2 (HTs), perhaps in steps of 2. This is useful, because
maximum HEPSPEC06 is often not coincident with slots == HTs.
(e.g. see Liverpool's readings for E5-2630 v2, where readings using 22
slots and 24 slots are provided. Similar for E5620.)
Also, nodes used for VAC are set with less slots/more mem per slots than
nodes used for Condor, because VMs have more overhead. It would be
superfluous and error prone to give the arithmetic for both/all sets.
Why not give the total memory? And the number of slots the figures
were calibrated for? The user can then derive all the information
he/she needs in (say) a spreadsheet or a script.
BTW: There is now no standard set of fields in that table. Perhaps there
should be?
Cheers,
Ste
--
Steve Jones [log in to unmask]
Grid System Administrator office: 220
High Energy Physics Division tel (int): 43396
Oliver Lodge Laboratory tel (ext): +44 (0)151 794 3396
University of Liverpool http://www.liv.ac.uk/physics/hep/
|