Presentation on theme: "FY 2004 Allocations Francesca Verdier NERSC User Services NERSC User Group Meeting 05/29/03."— Presentation transcript:
FY 2004 Allocations Francesca Verdier NERSC User Services NERSC User Group Meeting 05/29/03
2 FY 2004 ERCAP Timeline Thu June 5 ERCAP 2004 opens. NERSC sends out call for proposals. Wed July 23 (midnight) Submission deadline for ERCAP requests. July 31 – Aug 20Reviews take place. Mon Sept 15Award letters ed to PIs.
NERSC User Group Meeting 05/29/033 What’s New for FY 2004? – IBM SP Allocation Units In FY04 SP accounting will use raw SP processor hours rather than MPP hours. FY04 requests and awards will use units that are a factor of 2.5 smaller than last year. We expect to allocate 44 million SP hours. Maximum startup award: 12,000 20,000 SP hours (30,000 50,000 MPP hours). Minimum production awards remain at 20,000 SP hours (50,000 MPP hours).
NERSC User Group Meeting 05/29/034 What’s New for FY 2004 – Multi-year Awards and SRUs PIs requesting more than 400,000 raw hours (1 million MPP hours) per year will be able to request resources for up to three years. For such requests, DOE will decide how many years will actually be awarded. The way Storage Resource Units (SRUs) are now computed result in SRU charges being lower by about 13.9 percent on average that they were at the start of last year. See We expect to allocate 8.5 million SRUs.
NERSC User Group Meeting 05/29/035 What’s New for FY 2004 – User List Certification
NERSC User Group Meeting 05/29/036 ERCAP Code Performance Questions The code performance questions on the Request Form have been modified to be more specific about the information that is collected, and what platforms the questions pertain to. Seaborg code performance and scalability: For each of your major codes provide: – the gigaflops achieved over a range of node counts. Include the information for the largest number of nodes the code can effectively use, as well as node counts typically used in production. –the aggregate high-water memory (in gigabytes) used by that code for that number of nodes –the average wall time (1 to 48 hours) and expected number of runs
NERSC User Group Meeting 05/29/037 ERCAP Code Performance Questions (cont.)
NERSC User Group Meeting 05/29/038 ERCAP Code Performance Questions (cont.) If you do not typically run your codes on 64 or more nodes state the reasons. Are there any bottlenecks that NERSC can help overcome? If your parallel communication bandwidth or latency requirements are not met please describe your requirements. Also state the volume and rate of your inter-node messages. If current network bandwidth to/from NERSC does not meet your needs, describe your network requirements. If you have I/O requirements that aren't being adequately met at NERSC describe the I/O rates you are currently achieving and those you would like to achieve.
NERSC User Group Meeting 05/29/039 FY 2004 Review Process The CORP will review the following requests this year: –All DOE Base requests for >=400,000 SP hours, or >= 100,000 SRUs. –DOE Base projects requesting more than 150% of what they got in fy03. –Projects for which the PI requests a review. SciDAC requests will not be reviewed.