Hi Steve,
Daniela is quite right though on the page the various columns are quire
inconsistent and it would be useful to have the information. The
numbers of threads is not useful if it is not = number of job slots
since the HS06 value reported in the page should represent the latter.
cheers
alessandra
On 17/07/2017 13:31, Stephen Jones wrote:
> 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
>
>
>
>
>
>
>
>
>
--
Respect is a rational process. \\//
Fatti non foste a viver come bruti, ma per seguir virtute e canoscenza(Dante)
For Ur-Fascism, disagreement is treason. (U. Eco)
But but but her emails... covfefe!
|