SLAC Update Les Cottrell Richard Mount July 24

SLAC Update Les Cottrell & Richard Mount July 24, 2000 SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000

Ba. Bar • Very successful turn-on! – already reached design luminosity • Computing: – 1, 000 lines of C++ – Object oriented Db = Objectivity – Online data rate 10 -20 MBytes/sec – Regional computing centers: • IN 2 P 3 (France/Lyon), RAL (UK), INFN (Italy/Rome) SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 2

SLAC-Ba. Bar Data Analysis System 50/400 simultaneous/total physicists, 300 Tbytes per year SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 3

Ba. Bar Offline Computing at SLAC: Costs other than Personnel (does not include “per physicist” costs such as desktop support, help desk, telephone, general site network) Does not include tapes SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 4

Ba. Bar’s Need for the Grid Early 2000: – The Grid? “Don’t bother me now, I’m working on the CP-violation result for Osaka” – Data Transfer? “Something the French Ba. Barians do to justify the existence of their computer center” More recently: – “The Grid? Yes we need it and it has to work” SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 5

Ba. Bar’s Need for the Grid What Happened? – PEP II/Ba. Bar has reached design (integrated) luminosity (131 TB in database by end June 2000) – We all believe the plans to increase luminosity by a factor 8 by 2003 – Ba. Bar data will grow faster than “Moore’s Law” Options: – Pour French, British, Italian money into the SLAC Computer Center – Make the Grid work While simultaneously improving storage management SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 6

SSRL • Collaboration with SDSC (UC San Diego) – 130 MBytes/minute/beamline/full operation – 374 GBytes per 12 hour day for 4 beamlines – 90 TBytes per year (8 months operation) SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 7

Connectivity: NTON Demonstrated 57 MBytes/second disk to application between SLAC & LBNL a year ago. Now aiming for 100 MBytes/sec between SLAC & Caltech 2 x OC-12 (622 M) ATM 8 x OC-3 (155 M) ATM Nortel MUX Cisco GSR 12000 Nortel MUX HP Exemplar NTON ATM Gigabit Ethernet Catalyst 6509 2 x OC-12 (622 M) ATM NSTOR FC Array Dual PIII 833 w/Windows. NT Sun E 450 FC Disks SLAC Status, Les Cottrell Sun E 420 Dual PIII 533 w/Linux ESnet International Meeting, Kyoto July 24 -25, 2000 8

Connectivity: Stanford U/Abilene • OC 3 for last 9 months • Will upgrade to OC 12 soon • Currently only used between SLAC and Stanford and UC campuses – Important for SSRL – proposal to use for Qo. S tests between SLAC and Daresbury Lab in UK SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 9

Connectivity: ESnet 1 of 2 • ESnet: 43 Mbps being upgraded to 155 Mbps – upgrade requested 18 months ago, approved 15 months ago, hope for soon. . . – now saturated for long periods SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 10

Connectivity: ESnet 2 of 2 • Heavy use to transfer data from SLAC to IN 2 P 3 (1726 Mbps continuous, 100 GBytes/day, need TBytes/day) • No longer send tapes (latency goes from weeks to hours, less jitter, reduced labor (especially for errors)) • In past weakness of International links protected ESnet from significant traffic • HEP can saturate links between major regional centers • Other major Ba. Bar centers include: Oxford (RAL), Rome (INFN), Caltech, Colorado, LBNL, LLNL SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 11

Requirements • Higher speed end-to-end links • Site-to-Site Replication Service – 100 Mbyte/s goal possible through NTON (SLAC-Caltech are working on this). • Multi-site Cached File Access System – Will use OC 12, OC 3, (even T 3) as available • (even 20 Mbits/s international links) – Need “Bulk Transfer” service: • Latency unimportant • Tbytes/day throughput important (Need prioritized service to achieve this on international links) • Coexistence with other network users important. (This is the main PPDG need for differentiated services on ESnet) – can be background, don’t want onerous scheduling SLAC Status, Les Cottrell ESnet International Meeting, Kyoto July 24 -25, 2000 12