Demo Data from EDBT 2026 / reviewers in the wild / expert
Peter K. Szwed
dblp:48/717
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2004
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 50% Parallel and multicore computing · 50% | |
| Software engineering, system software, and programming languages
1 paper |
Compilers and program optimization · 100% |
Topics — the 5 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Distributed systems › fault tolerance
checkpointing |
0.0 | 1 | 2004 | Application-level checkpointing for shared memory programs · ASPLOS 2004 |
Distributed systems
fault tolerance |
0.0 | 1 | 2004 | Application-level checkpointing for shared memory programs · ASPLOS 2004 |
Parallel and multicore computing › parallel programming models › directive-based programming
OpenMP |
0.0 | 1 | 2004 | Application-level checkpointing for shared memory programs · ASPLOS 2004 |
Parallel and multicore computing › parallel programming models
shared-memory parallelization |
0.0 | 1 | 2004 | Application-level checkpointing for shared memory programs · ASPLOS 2004 |
Compilers and program optimization › program transformation
source-to-source transformation |
0.0 | 1 | 2004 | Application-level checkpointing for shared memory programs · ASPLOS 2004 |
Methods — techniques the papers use, named apart from their topics
runtime system · 0.1compiler instrumentation · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2004 | Application-level checkpointing for shared memory programsabstractTrends in high-performance computing are making it necessary for long-running applications to tolerate hardware faults. The most commonly used approach is checkpoint and restart (CPR) - the state of the computation is saved periodically on disk, and when a failure occurs, the computation is restarted from the last saved state. At present, it is the responsibility of the programmer to instrument applications for CPR.Our group is investigating the use of compiler technology to instrument codes to make them self-checkpointing and self-restarting, thereby providing an automatic solution to the problem of making long-running scientific applications resilient to hardware faults. Our previous work focused on message-passing programs.In this paper, we describe such a system for shared-memory programs running on symmetric multiprocessors. This system has two components: (i) a pre-compiler for source-to-source modification of applications, and (ii) a runtime system that implements a protocol for coordinating CPR among the threads of the parallel application. For the sake of concreteness, we focus on a non-trivial subset of OpenMP that includes barriers and locks.One of the advantages of this approach is that the ability to tolerate faults becomes embedded within the application itself, so applications become self-checkpointing and self-restarting on any platform. We demonstrate this by showing that our transformed benchmarks can checkpoint and restart on three different platforms (Windows/x86, Linux/x86, and Tru64/Alpha). Our experiments show that the overhead introduced by this approach is usually quite small; they also suggest ways in which the current implementation can be tuned to reduced overheads further. Greg Bronevetsky, Daniel Marques, Keshav Pingali, Peter K. Szwed, Martin Schulz 0001 |
ASPLOS | 4 |