Search NASA⌕ Search

SEARCH · Search NASA

Results for “APGAS”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

UPC++ Programmer’s Guide (v1.0 2017.9)

UPC++ is a C++11 library that provides Asynchronous Partitioned Global Address Space (APGAS) programming. It is designed for writing parallel programs that run efficiently and scale well on distributed-memory parallel computers. The APGAS model is single program, multiple-data (SPMD), with each separate thread of execution (referred to as a rank, a term borrowed from MPI) having access to local memory as it would in C++. However, APGAS also provides access to a global address space, which is allocated in shared segments that are distributed over the ranks. UPC++ provides numerous methods for accessing and using global memory. In UPC++, all operations that access remote memory are explicit, which encourages programmers to be aware of the cost of communication and data movement. Moreover, all remote-memory access operations are by default asynchronous, to enable programmers to write code that scales well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗

The UPC++ PGAS library for exascale computing. Extended Abstract

We describe UPC++ V1.0, a C++11 library that supports APGAS programming. UPC++ targets distributed data structures where communication is irregular or fine-grained. The key abstractions are global pointers, asynchronous programming via RPC, and futures. Global pointers incorporate ownership information useful in optimizing for locality. Futures capture data readiness state, are useful for scheduling and also enable the programmer to chain operations to execute asynchronously as high-latency dependencies become satisfied, via continuations. The interfaces for moving non-contiguous data and handling memories with different optimal access methods are composable and closely resemble those used in modern C++. Communication in UPC++ runs at close to hardware speeds by utilizing the low-overhead GASNet-EX communication library.

97 MATHEMATICS AND COMPUTING↗

Distribution Integrity Management Plan (DIMP): Los Alamos National Laboratory Natural Gas Distribution System

This document is the distribution integrity management plan (Plan) for the Los Alamos National Laboratory (LANL) Natural Gas Distribution System. This Plan meets the requirements of 49 CFR Part 192, Subpart P Distribution Integrity Management Programs (DIMP) for the LANL Natural Gas Distribution System. This Plan was developed by reviewing records and interviewing LANL personnel. The records consist of the design, construction, operation and maintenance for the LANL Natural Gas Distribution System. The records system for the LANL Natural Gas Distribution System is limited, so the majority of information is based on the judgment of LANL employees; the maintenance crew, the Corrosion Specialist and the Utilities and Infrastructure (UI) Civil Team Leader. The records used in this report are: Pipeline and Hazardous Materials Safety Administration (PHMSA) 7100.1-1, Report of Main and Service Line Inspection, Natural Gas Leak Survey, Gas Leak Response Report, Gas Leak and Repair Report, and Pipe-to-Soil Recordings. The specific elements of knowledge of the infrastructure used to evaluate each threat and prioritize risks are listed in Sections 6 and 7, Threat Evaluation and Risk Prioritization respectively. This Plan addresses additional information needed and a method for gaining that data over time through normal activities. The processes used for the initial assessment of Threat Evaluation and Risk Prioritization are the methods found in the Simple, Handy Risk-based Integrity Management Plan (SHRIMP™) software package developed by the American Pipeline and Gas Agency (APGA) Security and Integrity Foundation (SIF). SHRIMP™ uses an index model developed by the consultants and advisors of the SIF. Threat assessment is performed using questions developed by the Gas Piping Technology Company (GPTC) as modified and added to by the SHRIMP™ advisors. This Plan is required to be reviewed every 5 years to be continually refined and improved. Records for all piping system installed after the effective date of this Plan will be captured and retained in the UI records documentation system. Primary Utility Asbuilts are maintained by Utilities Mapping (UMAP) and additional records are maintained on the N drive. Engineering Change Notices (ECNs) are stored on the N drive under configuration management and kept up by Utilities and Infrastructure Division Office (UI-DO). Records include, at a minimum, the location where new piping and appurtenances are installed and the material of which they are constructed.

03 NATURAL GAS↗

UPC++ Specification v1.0, Draft 4

UPC++ is a C++11 library providing classes and functions that support Asynchronous Partitioned Global Address Space (APGAS) programming. We are revising the library under the auspices of the DOE’s Exascale Computing Project, to meet the needs of applications requiring PGAS support. UPC++ is intended for implementing elaborate distributed data structures where communication is irregular or fine-grained. The UPC++ interfaces for moving non-contiguous data and handling memories with different optimal access methods are composable and similar to those used in conventional C++. The UPC++ programmer can expect communication to run at close to hardware speeds. The key facilities in UPC++ are global pointers, that enable the programmer to express ownership information for improving locality, one-sided communication, both put/get and RPC, futures and continuations. Futures capture data readiness state, which is useful in making scheduling decisions, and continuations provide for completion handling via callbacks. Together, these enable the programmer to chain together a DAG of operations to execute asynchronously as high-latency dependencies become satisfied.

97 MATHEMATICS AND COMPUTING↗

Optimization of Asynchronous Communication Operations through Eager Notifications

UPC++ is a C++ library implementing the Asynchronous Partitioned Global Address Space (APGAS) model. We propose an enhancement to the completion mechanisms of UPC++ used to synchronize communication operations that is designed to reduce overhead for on-node operations. Our enhancement permits eager delivery of completion notification in cases where the data transfer semantics of an operation happen to complete synchronously, for example due to the use of shared-memory bypass. This semantic relaxation allows removing significant overhead from the critical path of the implementation in such cases. We evaluate our results on three different representative systems using a combination of microbenchmarks and five variations of the the HPCChallenge RandomAccess benchmark implemented in UPC++ and run on a single node to accentuate the impact of locality. We find that in RMA versions of the benchmark written in a straightforward manner (without manually optimizing for locality), the new eager notification mode can provide up to a 25% speedup when synchronizing with promises and up to a 13.5x speedup when synchronizing with conjoined futures. We also evaluate our results using a graph matching application written with UPC++ RMA communication, where we measure overall speedups of as much as 11% in single-node runs of the unmodified application code, due to our transparent enhancements.

Kamil, Amir↗

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↗