As for what the jobs do...
They perform a "typical" ATLAS user analysis, grabbing AOD files from
your ATLASMCDISK token on the local SE (in this case using the
https://twiki.cern.ch/twiki/bin/view/Main/FileStager method), doing
some analysis on them in Athena, and then considering the result.
Each job at a site operates on a different dataset, and isn't sent if
that dataset doesn't exist at the destination (so, that's why the
HammerCloud entries have a "submitted jobs" less than the number of
requested datasets), and the idea is that all the jobs run and pull
stuff from the SE at around the same time, thus providing suitably
realistic stress patterns.
Sam
2009/4/24 Daniela Bauer <[log in to unmask]>:
> Is there somewhere where we can see what these tests are actually
> meant to be doing ? Googling it didn't come up with much.
>
> Daniela
>
>
> 2009/4/24 Sam Skipsey <[log in to unmask]>:
>> Are you sure this isn't just the Extreme HammerCloud stressing your
>> SE? I notice that it (the HammerCloud) seems to be in a bit of an odd
>> state now, but it definitely submitted lots of jobs to everyone - we
>> got the normal high load at Glasgow when it passed through.
>>
>> Sam
>>
>> 2009/4/24 Christopher J.Walker <[log in to unmask]>:
>>> We have a high load (225) on our SE machine, and there are a large number of
>>> rfiod in the "D" state. We were also failing SAM tests earlier today -
>>> possibly because of this.
>>>
>>> Is this just that our SE is underpowered, or is it indicative of something
>>> having got stuck - would restarting dpm help for example?
>>>
>>> Chris
>>>
>>
>
>
>
> --
> -----------------------------------------------------------
> HEP Group
> Physics Dep
> Imperial College
> Tel: +44-(0)20-75947810
> http://www.hep.ph.ic.ac.uk/~dbauer/
>
|