Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Arash Rezaei

dblp:60/7906 · DBLP profile ↗
← Back
6ranked-venue papers
4as first author
1since 2021 · last 2024
0000-0003-2472-2414ORCID · corroborated

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 3 · 3 first-authorComputer networks · 1 · 1 since 2021Security and privacy · 1 · 1 first-authorSoftware 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
2 papers
Hardware accelerators and domain-specific architectures · 47% Distributed systems · 27% High-performance computing · 14%

Topics — the 6 heaviest of 7, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Hardware accelerators and domain-specific architectures
machine learning accelerator
0.812024
Resiliency at Scale: Managing Google's TPUv4 Machine Learning Supercomputer · NSDI 2024
High-performance computing
supercomputing
0.212024
Resiliency at Scale: Managing Google's TPUv4 Machine Learning Supercomputer · NSDI 2024
Distributed systems › fault tolerance
checkpointing
0.212014
Snapify: capturing snapshots of offload applications on xeon phi manycore processors · HPDC 2014
Distributed systems
fault tolerance
0.212014
Snapify: capturing snapshots of offload applications on xeon phi manycore processors · HPDC 2014
Processor architecture and microarchitecture
many-core architecture
0.212014
Snapify: capturing snapshots of offload applications on xeon phi manycore processors · HPDC 2014
Distributed systems › distributed system architecture › distributed operating systems
process migration
0.112014
Snapify: capturing snapshots of offload applications on xeon phi manycore processors · HPDC 2014

Methods — techniques the papers use, named apart from their topics

process swapping · 0.2process snapshot · 0.2RDMA · 0.2
YearPublicationVenuePosition
2024 Resiliency at Scale: Managing Google's TPUv4 Machine Learning Supercomputer
Yazhou Zu, Alireza Ghaffarkhah, Hoang-Vu Dang, Brian Towles, Steven Hand 0001, Safeen Huda, Adekunle Bello, Alexander Kolbasov, Arash Rezaei, Dayou Du, Steve Lacy, Aaron Wisner, Henri Bahini
NSDI9
2017 DINO: Divergent node cloning for sustained redundancy in HPC
Arash Rezaei, Frank Mueller 0001, Paul Hargrove, Eric Roman
J. Parallel Distributed Comput.1
2015 DINO: Divergent Node Cloning for Sustained Redundancy in HPC
abstract
Soft faults like silent data corruption and hard faults like hardware failures may cause a high performance computing (HPC) job of thousands of processes to nearly cease to make progress due to recovery overheads. Redundant computing has been proposed as a solution at extreme scale by allocating two or more processes to perform the same task. However, current redundant computing approaches do not repair failed replicas. Thus, SDC-free execution is not guaranteed after a replica failure and the job may finish with incorrect results. Replicas are logically equivalent, yet may have divergent runtime states during job execution, which complicates on-the-fly repairs for forward recovery. In this work, we present a redundant execution environment that quickly repairs hard failures via Divergent Node cloning (DINO) at the MPI task level. DINO contributes a novel task cloning service integrated into the MPI runtime system that solves the problem of consolidating divergent states among replicas on-the-fly. Experimental results indicate that DINO can recover from failures nearly instantaneously, thus retaining the redundancy level throughout job execution. The cloning overhead, depending on the process image size and its transfer rate, ranges from 5.60 to 90.48 seconds. To the best of our knowledge, the design and implementation for repairing failed replicas in redundant MPI computing is unprecedented.
Arash Rezaei, Frank Mueller 0001
CLUSTER1
2014 Snapify: capturing snapshots of offload applications on xeon phi manycore processors
abstract
Intel Xeon Phi coprocessors provide excellent performance acceleration for highly parallel applications and have been deployed in several top-ranking supercomputers. One popular approach of programming the Xeon Phi is the offload model, where parallel code is executed on the Xeon Phi, while the host system executes the sequential code. However, Xeon Phi's Many Integrated Core Platform Software Stack (MPSS) lacks fault-tolerance support for offload applications. This paper introduces Snapify, a set of extensions to MPSS that provides three novel features for Xeon Phi offload applications: checkpoint and restart, process swapping, and process migration. The core technique of Snapify is to take consistent process snapshots of the communicating offload processes and their host processes. To reduce the PCI latency of storing and retrieving process snapshots, Snapify uses a novel data transfer mechanism based on remote direct memory access (RDMA). Snapify can be used transparently by single-node and MPI applications, or be triggered directly by job schedulers through Snapify's API. Experimental results on OpenMP and MPI offload applications show that Snapify adds a runtime overhead of at most 5%, and this overhead is low enough for most use cases in practice.
Arash Rezaei, Giuseppe Coviello, Cheng-Hong Li, Srimat T. Chakradhar, Frank Mueller 0001
HPDC1
2014 Affinity-aware checkpoint restart
abstract
Current checkpointing techniques employed to overcome faults for HPC applications result in inferior application performance after restart from a checkpoint for a number of applications. This is due to a lack of page and core affinity awareness of the checkpoint/restart (C/R) mechanism, i.e., application tasks originally pinned to cores may be restarted on different cores, and in case of non-uniform memory architectures (NUMA), quite common today, memory pages associated with tasks on a NUMA node may be associated with a different NUMA node after restart. This work contributes a novel design technique for C/R mechanisms to preserve task-to-core maps and NUMA node specific page affinities across restarts. Experimental results with BLCR, a C/R mechanism, enhanced with affinity awareness demonstrate significant performance benefits of 37%-73% for the NAS Parallel Benchmark codes and 6-12% for NAMD with negligible overheads instead of up to nearly four times longer an execution times without affinity-aware restarts on 16 cores.
Ajay Saini, Arash Rezaei, Frank Mueller 0001, Paul Hargrove, Eric Roman
Middleware2
2010 Rejuvenating High Available Virtualized Systems
abstract
Virtualization technology in the form of server consolidation makes running of hot-standby replicas on one system possible, while software rejuvenation provides proactive recovery of failure. Both technologies have been used to make systems more dependable. However, the deployment of rejuvenation in virtualized systems had been limited only to virtual machines (VMs) or only to virtual machine monitors (VMMs), requiring changes to applications too. We propose a new rejuvenation technique for high available virtualized systems that is applied at both VM and VMM levels and yet it does not require any modifications to applications. Our proposition leverages the encapsulation of an application into a VM using this new combinatory rejuvenation technique that uses a time-based policy for VMM and a prediction-based policy for VMs. To demonstrate how much it can improve system availability, the stochastic reward net-based models of a typical virtualized consolidated server in cases of using a prediction-based policy, using a time-based policy, and using the proposed rejuvenation technique are presented and compared. We show that our method has higher system availability and lower downtime cost.
Arash Rezaei, Mohsen Sharifi
ARES1