1. Kent Milfeld, TACC TG Allocations Coordinator Aug. 13, 2009

2.  TRAC Request Summary Allocation Period (Oct. 1, 2009  Sept. 30, 2010)  Changes to TRAC Review Process  Issues with TG-Wide Roaming Access  TRAC Request Tracking

3. TRAC Requests RequestsAdaptiveAdvances TRAC Requests 1263312 Startup Trend Ja n FebMarAprMayJu n Jul Requests 68575261647774

4. Sept,2009 106

5. System#Reqs.Size Ranger69364M Kraken37326M Abe/QB3667M* LS73M Steele138M Cobalt83.8M Pople127.5M 30M *1 30M request

6.  Parallel Sessions at TRAC meeting (Trial)  Plenary Session for top 20 Requests.  2 Break-out Sessions: PHY/AST/ATM & MCB/CHE/DMR  Reconciliation Session: Adjust total allocation to availability  New Review Form addresses Methodology, Efficiency and Computational Plan Criteria  Better Reviewer/Request matching:  FOS (field of Science) matching  Reviewer Preference  Given Titles, reviewers are asked state their preference: Prefer, Indifferent, Unfamiliar

7. Rating Recommendation (Overall Evaluation) Reference to Criteria Methodology (Algorithms, Packages, Libraries) Efficiency (Performance, Optimization Scaling) Computational Plan (SU Calculations, Justification)

8.  Now Using Google docs to Track Monitoring.  Startups  Supplement/Justification/Advances  Responsibility for Processing can be shared.  Site Reps can easily see/determine status.  Can be used as “case study”/prototype for an enhanced POPS Interface.

10.  Roaming Problems  Charging Algorithm on disparate platforms (up to 2x difference).  Not all systems are available through Roaming Access  Difficult for sites to plan for throughput  Big difference between availability on SMP and Clusters (See  )

11.  TG-Wide Roaming Access  Has evolved into ineffective mechanism.  Mid-range system Pool ?  Abe (NCS), QueenB (LONI), Lonestar (TACC), Steele (Purdue)  Serious RP concerns about managing user expectations.

12.  Remove TG-Roaming from Resource Request form.  Possible Modes of Multi-system Access (Lone*/Abe/QB/Steele):  Select distribution on Individual Systems If necessary, distribution can be readjusted through transfers.  Single Pool Allow user to request allocation of all 4 systems as a single allocation.  Co-Allocation + Individual Allow users to select from pool, but allocation usage on any single system is limited to a set “distribution” percentage. If necessary, percent distribution can be readjusted through redistribution. Or, Select distribution on Individual Systems.

13.  Questions?