> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Andrew McNab
>
> And the ATLAS dashboard can give you CPU time used per-site or per
> CE/queue combination, which gets us back to the original email.
>
> Going by what is visible today, are there any other options for getting
> CPU time for analyis and for production jobs per site (ideally per-
> subcluster eg via the CE/queue name since CPU model isn't available on the
> dashboard)?
>
So for the time being we're just going to go for an average HS06 value
and not worry about doing the specific per node cupid->HS06 thing?
> If not, I think we should collect the list of CE-queue name to
> HEPSPEC06/core mappings from sites so Steve can get that working.
>
My understanding of the currently available information is that
the benchmark value published in GlueHostProcessorOtherDescription
should be the weighted average for the CPUs behind a CE, and should not
be scaled. If my understanding is correct then I think that's the value
that you're looking for.
> Ideally, yes, something like an environment variable with the HEPSPEC06
> figure to be accounted by each job, recorded by the job and passed up the
> chain and delivered as per-site totals would be best. But that is going to
> involve changes in multiple levels of ATLAS's chain of stuff and we need
> something up and running pretty much now to give people fair notice before
> the start of May.
>
Right; we should bring this plan up at the GDB though and get a generally
standardized place to put it, then get it deployed and it'll then be there
in the future for things to use.
Ewan
|