Difference between revisions of "Atlas"

Un article de lcgwiki.
Jump to: navigation, search
Ligne 73: Ligne 73:
  
 
* Next steps
 
* Next steps
 +
** Deploy Rucio 1.17 to use protocol priority defined in AGIS (bug in 1.16). Solving bug : use most trusted protocol and would help to control srm decreasing usage
 
** Monitor job efficiency vs RTT between SE and WN -> Identify when cache does not have impact (assuming no network bandwidth limitation)
 
** Monitor job efficiency vs RTT between SE and WN -> Identify when cache does not have impact (assuming no network bandwidth limitation)
 
** Understand the ATLAS job borkering algorithm
 
** Understand the ATLAS job borkering algorithm

Version du 16:18, 15 septembre 2018

Bienvenue sur la page Atlas LCG-France
Welcome to the LCG-France Atlas page

DOMA_FR tests

  • Global transfers from/ to (same site dest/source site excluded)
Header text LAPP LPSC CC
From

Link

Link

Link

To

Link

Link

Link

  • Data access monitorings per WN
Destination of access LAPP LPSC CC
Production download

Link

Link

Link

Production input

Link

Link

Link

Analysis Download

Link

Link

Link

Analysis Direct Access

link

Link

Link

  • Current conclusion
    • Enabling direct access creates much more network usage -> Is it usefull for ATLAS ? (processing urgent request faster ?)
    • Job brokering prefers direct access than Rucio/FTS transfer
    • 10 Gb/s connection LAPP-CC (used for all LAPP WAN transfers to any site) can get saturated if huge amount of jobs starting at same time (No smoothing by Panda)
  • Next steps
    • Deploy Rucio 1.17 to use protocol priority defined in AGIS (bug in 1.16). Solving bug : use most trusted protocol and would help to control srm decreasing usage
    • Monitor job efficiency vs RTT between SE and WN -> Identify when cache does not have impact (assuming no network bandwidth limitation)
    • Understand the ATLAS job borkering algorithm