-- HarryRenshall - 06 Mar 2006

Last Updated 01.06.2007: Add in 3D database disk requirements and ATLAS quantitative requirements for 3Q.

Updated 1.03.2007: Precise plans for Atlas February/March Data Distribution tests (see https://twiki.cern.ch/twiki/bin/view/Atlas/TierZero20071). Change Atlas share from 5.3% to 4.3%.

Updated 15.01.2007: Move the ATLAS Tier0 export tests from 15 Jan to new preliminary date of end Feb.

Updated 17.11.2006: For ATLAS revise (downwards, especially in disk) MC requirements for first half of 2007.

Updated 2.11.2006: For ATLAS revise 4Q2006 MC requirements, add MC plans up to mid-2007 and add January 2007 Tier-0 and export exercise.

Updated 21 August to continue ATLAS data export till end September.

Updated 12 June to update Atlas June plans.

TRIUMF-Vancouver Site Resource Requirements Timetable for 2006/2007

Tier 1 TRIUMF-Vancouver. To provide 4.3% of Atlas resources  
Month ATLAS Requirements Tier 0 Requirements
April Provide 47 KSi2K of cpu for MC event generation and 3 TB of disk and 7 TB of tape for MC data this quarter 3rd to 16th CERN disk-disk at 50 MB/sec. 18th to 24th CERN disk-tape at 50 MB/sec
May Provide 47 KSi2K of cpu for MC event generation CERN background disk-disk top up to 50MB/sec
June Provide 47 KSi2K of cpu for MC event generation. From 19 June to 7 July T0 to T1 tests take 17.0 MB/sec "Raw" to tape (rate to be reported), ESD at 10.6 MB/s to disk and AOD at 20 MB/s to disk from Tier 0 (total rate 47.6 MB/s). These data can be deleted after 24 hours CERN background disk-disk top up to 50MB/sec
July Provide 50 KSi2K of cpu for MC event generation and 4 TB of disk and 9 TB of tape for MC data this quarter. "Raw" reconstruction setting up - stagein from tape using 1-2 drives CERN background disk-disk top up to 50MB/sec
August Provide 50 KSi2K of cpu for MC event generation. Two slots of 3 days of "raw" reconstruction - stagein from tape using 1-2 drives. Analysis tests - 20 MB/sec incoming - will include scalability tests and prefers to be only Atlas grid activity. Take 17.0 MB/sec "Raw" to tape (rate to be reported), ESD at 10.6 MB/s to disk and AOD at 20 MB/s to disk from Tier 0 (total rate 47.6 MB/s). These data can be deleted after 24 hours CERN background disk-disk top up to 50MB/sec
September Provide 50 KSi2K of cpu for MC event generation. Take 17.0 MB/sec "Raw" to tape (rate to be reported), ESD at 10.6 MB/s to disk and AOD at 20 MB/s to disk from Tier 0 (total rate 47.6 MB/s). These data can be deleted after 24 hours CERN background disk-disk top up to 50MB/sec.
October Reprocessing tests - 20 MB/sec incoming CERN background disk-disk top up to 50MB/sec
November Provide 69 KSi2K of cpu and an additional 1.6 TB of permanent disk and 1.0 TB of temporary (till reconstruction is run) disk plus an additional 1.6 TB of permanent tape storage for MC event generation. Analysis tests - 20 MB/sec incoming at the same time as reprocessing continues CERN background disk-disk top up to 50MB/sec
December Provide 69 KSi2K of cpu and an additional 1.6 TB of permanent disk and 1.0 TB of temporary (till reconstruction is run) disk plus an additional 1.6 TB of permanent tape storage for MC event generation. CERN background disk-disk top up to 50MB/sec
January 2007 Provide 92 KSi2K of cpu each month and an additional 6.4 TB of permanent disk plus an additional 6.4 TB of permanent tape storage for this quarter for MC event generation. CERN background disk-disk top up to 50MB/sec
February Provide 92 KSi2K of cpu for MC event generation. CERN background disk-disk top up to 50MB/sec
March Provide 92 KSi2K of cpu for MC event generation. From 12 March begin 2 week data distribution tests. Rampup to full 2008 rate from Tier 0 during first week. Raw from Tier 0 to reach 14 MB/s, ESD to reach 17 MB/s and AOD to reach 20 MB/s. Raw data to go to tape then can be recycled. ESD and AOD to go to disk and can be recycled but during last two weeks AOD should be distributed to associated Tier 2, requiring up to 5.2 TB of disk buffer, before being recycled. From 26 March participate in all-experiment service challenge milestone taking 65% of the average 2008 rate as above but without AOD redistribution for the next 7 days. CERN background disk-disk top up to 50MB/sec
April Provide 184 KSi2K of cpu each month and an additional 12.9 TB of permanent disk plus an additional 13 TB of permanent tape storage for this quarter for MC event generation. Provide a permanent 300 GB of disk space for ATLAS conditions and event tag databases. CERN background disk-disk top up to 50MB/sec
May Provide 184 KSi2K of cpu for MC event generation. Repeat February/March data distribution tests. CERN background disk-disk top up to 50MB/sec
June Provide 184 KSi2K of cpu for MC event generation. CERN background disk-disk top up to 50MB/sec
July Start full scale (2008 running) dress rehearsal. CERN background disk-disk top up to 50MB/sec
August Continue rampup of full scale dress rehearsal. CERN background disk-disk top up to 50MB/sec
September Reach rates of full scale dress rehearsal. Take raw data from CERN (raw is to go to tape) at 13.8 MB/sec, ESD at 17.2 MB/sec and AOD at 20 MB/sec. Send and receive data from Tier-1 and Tier-2 according to the Megatable spreadsheet values (see link on first page of this Twiki). CERN background disk-disk top up to 50MB/sec
October Stable running of full scale dress rehearsal. CERN background disk-disk top up to 50MB/sec
November Engineering run. Provide a permanent 1000 GB of disk space for ATLAS conditions and event tag databases. CERN background disk-disk top up to 50MB/sec
December Engineering run. CERN background disk-disk top up to 50MB/sec
Edit | Attach | Watch | Print version | History: r23 | r21 < r20 < r19 < r18 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r19 - 2007-06-01 - HarryRenshall
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback