Search NASA⌕ Search

Engineering topics

Shet, Aniruddha G

Publications and source records attributed to Shet, Aniruddha G.

Strategies for Fault Tolerance in Multicomponent Applications

This paper discusses on-going work with the Integrated Plasma Simulator (IPS), a framework for coupled multiphysics simulations of plasmas, to allow simulations to run through the loss of nodes on which the simulation is executing. While many different techniques are available to improve the fault tolerance of computational science applications on high-performance computer systems, checkpoint/restart (C/R) remains virtually the only one that see widespread use in practice. Our focus here is to augment the traditional C/R approach with additional techniques that can provide a more localized and tailored response to faults based on the ability to restart failed tasks on an individual basis, and the use of information external to the application itself in order to guide decision-making, in many cases avoiding the need to stop and restart the entire simulation. This capability involves several features within the IPS framework, and leverages the Fault Tolerance Backplane, a publish/subscribe event service to disseminate fault-related information throughout HPC systems, to obtain information from the Reliability, Availability and Serviceability (RAS) subsystem of the HPC system. This work is described in the context of Cray XT-series computer systems for concreteness, but is applicable to other environments as well. As part of the analysis of this work, we discuss the requirements to generalize this approach to other complex simulation applications beyond the Integrated Plasma Simulator.

99 GENERAL AND MISCELLANEOUS↗

Many-Task Applications in the Integrated Plasma Simulator

This paper discusses the Integrated Plasma Simulator (IPS), a framework for coupled multiphysics simulation of fusion plasmas, in the context of many-task computing. The IPS supports multiple levels of parallelism: individual computational tasks can be parallel, components can launch multiple tasks concurrently, tasks from multiple components can be executed concurrently within a simulation, and multiple simulations can be run simultaneously. Each level of parallelism is constructed on top of the many-task computing capabilities implemented in the IPS, the foundation for the parallelism presented at the multiple simulation level. We show that a modest number of simultaneous simulations, with appropriately sized resource allocations, can provide a better trade-off between resource utilization and overall execution time than if they are run as separate jobs. This approach is highly beneficial for situations in which individual simulation tasks may differ significantly in parallel scalability, as is the case in many scientific communities where coupled simulations rely substantially on legacy code.

99 GENERAL AND MISCELLANEOUS↗

The Design and Implementation of the Swim Integrated Plasma Simulator

As computing capabilities have increased, the coupling of computational models has become an increasingly viable and therefore important way of improving the physical fidelity of simulations. Applications currently using some form of multicode or multi-component coupling include climate modeling, rocket simulations, and chemistry. In recent years, the plasma physics community has also begun to pursue integrated multiphysics simulations for space weather and fusion energy applications. Such model coupling generally exposes new issues in the physical, mathematical, and computational aspects of the problem. This paper focuses on the computational aspects of one such effort, detailing the design, and implementation of the Integrated Plasma Simulator (IPS) for the Center for Simulation of Wave Interactions with Magnetohydrodynamics (SWIM). The IPS framework focuses on maximizing flexibility for the creators of loosely-coupled component-based simulations, and provides services for execution coordination, resource management, data management, and inter-component communication. It also serves as a proving ground for a concurrent 'multi-tasking' execution model to improve resource utilization, and application-level fault tolerance. We also briefly describe how the IPS has been applied to several problems of interest to the fusion community.

33 ADVANCED PROPULSION SYSTEMS↗

Asynchronous Programming in UPC: A Case Study and Potential for Improvement

In a traditional Partitioned Global Address Space language like UPC, an application programmer works with the model of a static set of threads performing locality-aware accesses on a global address space. On the other hand, asynchronous programming provides a simple interface for expressing the concurrency in dynamic, irregular algorithms, with the prospect of efficient portable execution from sophisticated runtime schemes handling the exposed concurrency. In this paper, we adopt the asynchronous style of programming to parallelize a nested, tree-based code in UPC. To maximize performance without losing the ease of application programming, we design Asynchronous Remote Methods as a potential extension to the UPC standard. Our prototype implementation of this construct in Berkeley UPC yields within 7% of ideal performance and 20-fold improvement over the original Standard UPC solution in some cases.

97 MATHEMATICS AND COMPUTING↗

Extending the Concept of Component Interfaces: Experience with the Integrated Plasma Simulator

In the component approach, components are said to interact through well-defined interfaces. Conventionally, these interfaces are based on method signatures which define the syntax, if not the semantics of the interface. However in many cases, this does not encompass all of the interactions a component has with its peers. In the Integrated Plasma Simulator (IPS), a framework for coupled simulation of fusion plasmas developed by the Center for Simulation of RF Wave Interactions with Magnetohydrodynamics (SWIM), we find that components interact through files and through an event service in addition to the usual method calls. In this report, we discuss the motivations for the design of the IPS and our experience with it. We further consider whether the concept of a component interface needs to be extended, and how it might be done. Component-based software engineering (CBSE) has allowed applications to grow in size, scale and power, by coupling components along well-defined interfaces. Many groups have come together to provide rules and standards for component and interface definitions. General purpose component architectures have been designed for business, and scientific computing, while domain specific component frameworks have been created in many domains, including climate modeling, rocket simulation, and engineering. In each architecture, component interfaces, typically implemented as method invocations, are the only ways that are mentioned for components to interact with each other and the outside world. However, components may not always communicate over their interfaces. They can interact with software entities in many other ways including sharing files and publish/subscribe systems. In this paper we consider two ways in which components interact without method invocation in a component framework, how the component interface can be extended to describe these interactions, and the implications on the greater component community. The rest of the paper continues as follows: first we briefly describe the fusion simulation framework that serves as the basis for the discussion (Sec. 2), followed by a description of non-interface interactions (Sec. 3), a discussion of how to extend to the component interface (Sec. 4) and finally some conclusions (Sec. 5).

33 ADVANCED PROPULSION SYSTEMS↗