> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
>
> That was the initial idea, but the HEPSPEC06 figure depends on more than
> the CPU model and MHz (eg the kernel version) so it would need to be at
> least per-site, and really per subcluster. That just gets us back to the
> CE-queue mapping, which is something Steve's script can do without having
> to modify what ATLAS makes available via the dashboard jobsummary.
>
The per resource mapping is going to be a worse approximation than the
cpuid is, so switching to this on the grounds that the cupid->HEPSPEC06
mapping isn't 100% seems strange.
We did raise the possibility of putting each nodes' HEPSPEC06 in an
environment variable from whence the pilot could grab it directly -
would that be better?
Ewan
|