2017 IEEE/ACM International Conference on Computer-Aided Design (ICCAD) 2017
DOI: 10.1109/iccad.2017.8203853
|View full text |Cite
|
Sign up to set email alerts
|

DtCraft: A distributed execution engine for compute-intensive applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
5
1
1

Relationship

1
6

Authors

Journals

citations
Cited by 12 publications
(2 citation statements)
references
References 7 publications
0
2
0
Order By: Relevance
“…Our design philosophy is to provide users a centralized viewpoint of the entire distributed system. The distributed timer consists of a master daemon that manages agent daemons running on each cluster node, and timer instances that are coordinated by these agents [11] [3] [4]. A timer instance is a local timer that runs on a single design partition and persists in memory through an eventdriven loop.…”
Section: Proposed Distributed Timermentioning
confidence: 99%
“…Our design philosophy is to provide users a centralized viewpoint of the entire distributed system. The distributed timer consists of a master daemon that manages agent daemons running on each cluster node, and timer instances that are coordinated by these agents [11] [3] [4]. A timer instance is a local timer that runs on a single design partition and persists in memory through an eventdriven loop.…”
Section: Proposed Distributed Timermentioning
confidence: 99%
“…Traditionally, based on the different utilization of resources, jobs can be generally classified into three categories: I/O intensive, memory intensive, and compute-intensive [20]. By far, a majority of previous studies treat CPU as the main resource consumed by compute-intensive jobs [21][22][23]. But, as the emergence of deep learning, the job type can be specifically divided into CPU-intensive and GPU-intensive.…”
Section: Introductionmentioning
confidence: 99%