Draft statement of work
Sequoia Timescale and High Level Deliverables
Download 0.66 Mb.
|
- Navigate this page:
- 2.0Sequoia High-Level Hardware Requirements
1.8Sequoia Timescale and High Level DeliverablesBuilding and delivering a petascale computing resource of this scale is a daunting task. The successful completion of this project will require close collaboration between the selected Offeror and LLNS. It requires careful planning and coordination of these efforts within the selected Offeror and LLNS partnership. To this end, LLNS anticipates that the project will take on several critical stages: 1) formation of the selected Offeror / LLNS partnership; 2) Dawn Demo; 3) Deployment of the Dawn system for ASC application code development and scaling; 4) demonstrate the Sequoia prototype hardware and software capabilities with Sequoia benchmarks; 5) LLNS decision on the size of Sequoia system to build (Sequoia or Sequoia14, see section 2.12); 6) demonstrate a peak (petaFLOP/s) plus weighted sustained performance (application specific figure-of-merit) of at least forty (40.0) on the five ASC Sequoia Marquee application benchmarks; 7) Sequoia deployment to the program as the ASC Tri-Laboratory capability platform; 8) Sequoia deployment to the ASC Program as a general purpose production resource; and 9) final retirement of the Sequoia platform after five years of use from the time of acceptance. The table below gives general progress metrics for the successful completion of the Sequoia subcontract(s). These metrics include target dates based on ASC programmatic requirements and anticipated fiscal year funding. These target dates are not mandatory and can be modified to more closely match an Offeror’s product roadmap. However, there is a significant value to LLNS and the ASC Program to timely delivery of the proposed system and computing capability.
End of Section 1 2.0Sequoia High-Level Hardware RequirementsThe end product of the selected Offeror’s ASC Sequoia development and engineering activity will be a balanced compute resource 24 times more powerful than ASC Purple on the ASC Integrated Design Codes (IDC) and 25-50 times more powerful than BlueGene/L (65,536 node configuration) on ASC Scientific Applications currently available within the ASC Tri-Laboratory community. It will be focused on solving the critical stockpile stewardship problems, that is, the large-scale application problems at the edge of the ASC Program’s understanding of weapon physics. This fully functional Sequoia system must be useful in the sense of being able to deliver a large fraction of peak performance to a diverse scientific and engineering workload. It must also be useful in the sense that the code development and production environments are robust and facilitate the dynamic workload requirements. The specifications below define a Sequoia scalable system with peak of at least 20 petaFLOP/s. Offeror should provide an estimate of the proposed Sequoia system sustained performance on ASC marquee benchmarks (measured as a weighted average of the figure-of-merit for these codes) based on the performance of the marquee demonstration codes identified in Section 9.1.1. The physics and numerical analysis algorithms and coding styles of these codes are indicative of key portions of the overall stockpile stewardship workload. Obviously, Offeror may necessarily have to estimate the efficiency of the marquee applications on the proposed system in order to determine what to actually bid, price and ultimately deliver to meet the mandatory requirement identified in Section 2.1. If the delivered performance of the marquee applications on the proposed system is below the Offeror’s estimates, then more than 20.0 petaFLOP/s of peak computational resources will be required, and scaled as defined in Section 2.3. In LLNS’ view, this issue will motivate additional Offeror innovation during subcontract performance. Due to the classified ASC programmatic requirements both the Sequoia and Dawn systems will be initially deployed in the unclassified (BLACK) network environment and, once accepted and stabilized, migrated to, and be gainfully employed in, the classified (RED) network environment. Development of the Dawn and Sequoia systems may comply with the requirements identified in section 8, Project Management. There is only one mandatory requirement for Sequoia, Section 2.1 “Sequoia System Peak”. There is only one mandatory option requirement for Sequoia, Section 2.12.3 “ Sequoia14 System Performance.” The specific hardware and software Target Requirements the Sequoia system may meet are delineated in Sections 2 and 3, respectively, with (TR-1, TR-2 and TR-3) designation with TR-1 being highest priority and TR-3 being lowest. Target Options (TO-1, TO-2) are specific hardware configurations described in Section 2.12 that LLNS has identified as options that may be advantageous for the ASC program. In addition to the highest priority hardware and software targets or options, the Offeror may deliver any Target Requirements (TR-2 and TR-3) for the Sequoia system, and any additional features consistent with the objectives of this project and Offeror’s Research and Development Plan, which the Offeror believes will be of benefit to the project. Offeror’s technical proposal Section 2 will contain a detailed description of the proposed Sequoia System. It may include a detailed discussion of how all of the Baseline Characteristics (MR, MO, TRs, and TOs) will be met, as well as a discussion of LLNS and Offeror identified Value-Related Characteristics included in the technical solution. Download 0.66 Mb. Share with your friends:
|