1 / 6

RAC requirements

RAC requirements. D0RACE meeting March 2002. Location issues. Should follow more or less collaborators distribution Locations should be defined to avoid unnecessary network traffic overlap. Network Bandwidths.

bianca
Télécharger la présentation

RAC requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RAC requirements D0RACE meeting March 2002 F.Filthaut/B.Thooris D0RACE meeting March 2002

  2. Location issues • Should follow more or less collaborators distribution • Locations should be defined to avoid unnecessary network traffic overlap F.Filthaut/B.Thooris D0RACE meeting March 2002

  3. Network Bandwidths • Stringent requirements needed for bandwidth to FNAL (as this is where the centers have to get much of their initial data from) • Sustained rate of 10 Mbyte/s bound to require at least 1Gbit/s line • High bandwidth to other RACs desirable ( fair amount of data have to be shipped between centers ) • High bandwidth to IACs also desirable ( for those institutes that want to be able to look at data “at home” ) Perhaps less urgent if IAC’s needs can also be served by processing at the RACs • But serving IACs may require even higher bandwidth than transfers from FNAL? F.Filthaut/B.Thooris D0RACE meeting March 2002

  4. Storage Cache Size • Sufficient storage place is needed to hold 10~20% of data permanently and must be expandable to accomodate data increase • 30TB (300TB) just for 10% of RunIIa (RunIIb) Raw data... • 10TB (100TB) for RunIIa (RunIIb) Thumbnail set • Compute required cache size based on Thumbnails and some fraction of raw/reco • Random access could be preferred, since Thumbnails will likely be often used • 400 TB ~ 100-200k$?? Or what about tape (& robot) costs? F.Filthaut/B.Thooris D0RACE meeting March 2002

  5. Computer Processing Infrastructure • RACs must have sufficient computing power to reprocess all its data within 4 to 6 weeks • RunIIa: 2·108 evts/1month at 10s/event: ~ 800 CPU’s • Don’t believe it’s realistic to expect the same turn-around for RIIb • CPU resources could be different for each RAC according to the number of IACs in the area • i.e. assume (part of) IAC processing done at RAC. This implies point (1) above only gives a lower limit? Otherwise reduce “user” access during this time? • Requests can also be done by other RACs (?) F.Filthaut/B.Thooris D0RACE meeting March 2002

  6. Support personnel • A relevant study must be done to estimate the support personnel in each RAC in order to : • manage the software distribution • provide the support for users • address security issues? • maintain hardware • RAC must have a mirror copy of CVS database for synchronize update between RAC and CAC • RAC must also keep the relevant copies of databases • if caching turns out not to work • RAC must act as a SAM service station to provide data and rootuples to IACs F.Filthaut/B.Thooris D0RACE meeting March 2002

More Related