Papers › DeFiNES: Enabling Fast Exploration of the Depth-first Scheduling Space for DNN...

DeFiNES: Enabling Fast Exploration of the Depth-first Scheduling Space for DNN Accelerators through Analytical Modeling

10 Dec 2022arXiv:2212.05344links table onlyarchive 2025-07-28

Linyan Mei, Koen Goetschalckx, Arne Symons, Marian Verhelst

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

DNN workloads can be scheduled onto DNN accelerators in many different ways: from layer-by-layer scheduling to cross-layer depth-first scheduling (a.k.a. layer fusion, or cascaded execution). This results in a very broad scheduling space, with each schedule leading to varying hardware (HW) costs in terms of energy and latency. To rapidly explore this vast space for a wide variety of hardware architectures, analytical cost models are crucial to estimate scheduling effects on the HW level. However, state-of-the-art cost models are lacking support for exploring the complete depth-first scheduling space, for instance focusing only on activations while ignoring weights, or modeling only DRAM accesses while overlooking on-chip data movements. These limitations prevent researchers from systematically and accurately understanding the depth-first scheduling space. After formalizing this design space, this work proposes a unified modeling framework, DeFiNES, for layer-by-layer and depth-first scheduling to fill in the gaps. DeFiNES enables analytically estimating the hardware cost for possible schedules in terms of both energy and latency, while considering data access at every memory level. This is done for each schedule and HW architecture under study by optimally choosing the active part of the memory hierarchy per unique combination of operand, layer, and feature map tile. The hardware costs are estimated, taking into account both data computation and data copy phases. The analytical cost model is validated against measured data from a taped-out depth-first DNN accelerator, DepFiN, showing good modeling accuracy at the end-to-end neural network level. A comparison with generalized state-of-the-art demonstrates up to 10X better solutions found with DeFiNES.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology: its repositories, every harvested function with whether it ran, its licence and the call to fetch it.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2212.05344")

Code

Syntology Ran 6 of 9 code samples harvested from 3 repositories linked to this paper; 3 have no recorded run. Of those that ran: 6 ran with no contract checked.

By repository: official repository: 2 samples from 1 repository, 2 ran; community (archive-listed): 7 samples from 2 repositories, 4 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

zigzag-project/defines officialmentioned in papermentioned on GitHubBSD-3-Clause report
ZigZag-Project/zigzag mentioned on GitHubMIT report
kuleuven-micas/acco mentioned on GitHubBSD-3-Clause report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

9 samples harvested; 6 ran; 0 honoured the contract we drafted; 3 have no recorded run. Read from Syntology's graph 2026-09-25; that is when this build read the record, not when the samples ran.

6ran
3unverified

Licence: 0 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; each sample names its own and says which. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

annotate_heatmap zigzag-project/defines/plot_helper_funcs.py official repository ran BSD-3-Clause (permissive) · 270a7a067a1c0319 · report
heatmap zigzag-project/defines/plot_helper_funcs.py official repository ran BSD-3-Clause (permissive) · cfe5673960d811ad · report
extract_port_latency kuleuven-micas/acco/classes/depthfirst/data_copy_layer.py community (archive-listed) ran BSD-3-Clause (permissive) · 528110165dfbbbed · report
hash_sha512 ZigZag-Project/zigzag/zigzag/utils.py community (archive-listed) ran MIT (permissive) · fe45575f66dbe74b · report
pickle_deepcopy ZigZag-Project/zigzag/zigzag/utils.py community (archive-listed) ran MIT (permissive) · 979d8736de4592ce · report
pickle_deepcopy kuleuven-micas/acco/utils.py community (archive-listed) ran BSD-3-Clause (permissive) · c54085ffaf8bf13f · report
calc_MUW_union kuleuven-micas/acco/classes/cost_model/cost_model.py community (archive-listed) unverified BSD-3-Clause (permissive) · 9247aaa762351759 · report
get_shared_mem_list kuleuven-micas/acco/classes/cost_model/cost_model.py community (archive-listed) unverified BSD-3-Clause (permissive) · f133edb257d3344c · report
pickle_save ZigZag-Project/zigzag/zigzag/utils.py community (archive-listed) unverified MIT (permissive) · 10a1b5d040c1c4cb · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections