Difference between revisions of "Atlas:Analysis Challenge"

Un article de lcgwiki.
Jump to: navigation, search
(First exercise on the FR Cloud in december 08 (proposition))
(Goals)
Ligne 2: Ligne 2:
  
 
==== Goals ====
 
==== Goals ====
Validation of site and cloud readiness for Analysis 
 
 
* measure "real" analysis job efficiency and turn around on several sites of a given cloud
 
* measure "real" analysis job efficiency and turn around on several sites of a given cloud
 
* measure data access performance  
 
* measure data access performance  

Version du 10:00, 21 novembre 2008

ATLAS Analysis challenge

Goals

  • measure "real" analysis job efficiency and turn around on several sites of a given cloud
  • measure data access performance
  • check load balancing between different users and different analysis tools (Ganga vs pAthena)
  • check load balancing between analysis and MC production

First exercise on the FR Cloud in december 08 (proposition)

DA challenges have been performed on IT and DE clouds in october 08. Proposition has been made to extend this cloud-by cloud challenge to the FR Cloud. See ATLAS coordination DA challenge meeting (Nov. 20)

First exercise will help to identify breaking points and bottlenecks. It is limited in time (a few days) and requires careful attention of site administrators during that period,in particular network (internal & external), disk, cpu monitoring. It is not a functional test but more a scaling test to identify breaking points and bottleneck in the cloud configuration.

This first try can be run centrally. ATLAS coordination (Dan van der Ster and Johannes Elmsheuser) needs to know which sites to be tested and when. Any site in the Tiers_of_ATLAS list can participate.

Procedure

Testing framework and conditions

The testing framework is ganga-based. It is currently using LCG backend but it will soon be possible to use PANDA backend as well.

It is possible for sites to limit the number of jobs sent at a time. 
DA team is open to suggestion and ready to take into account 
site constraints or limitations.

2009 plans

Results

See