Hi Rob,
> Conversely, if we publish the number of hyperthreads and the
> appropriate HS06, the size and composition of the cluster will also be
> accurate (for hyperthreading), but our accounting would be
> significantly understated.
>
This is what Manchester is doing following the Glue schema. Of course we
loose out when the cluster is half full but we try to keep it full and
we use all the 24 slots so not being full is less systematic than what
you want to do.
>
> The logical thing to do would seem to be to publish the number of jobs
> run per CPU (8, in this instance) as cores/hyperthreads and the
> appropriate HS06, in which case the total size of the cluster and the
> accounting would be accurate (when we're full of jobs anyway), but the
> physical composition would not be (which seems least important to me).
> But as mentioned, the schema seems to forbid this.
we decided to run less jobs this is the solution I'd argue for too.
cheers
alessandra
|