Abstract 1 Introduction 2 System Model 3 Task Classification and Overview 4 Probabilistic DAG Clustering 5 Clustering Optimization 6 Evaluation 7 Related Work 8 Conclusion References

Probabilistic Schedulability Analysis for Mixed-Criticality DAG Tasks on Multiprocessors

Hiroto Takahashi ORCID Graduate School of Science and Engineering, Saitama University, Japan    Atsushi Yano ORCID Graduate School of Science and Engineering, Saitama University, Japan
TIER IV Inc., Tokyo, Japan
   Takuya Azumi ORCID Graduate School of Science and Engineering, Saitama University, Japan
TIER IV Inc., Tokyo, Japan
Abstract

Mixed-criticality DAG task systems on multiprocessors require schedulability analysis to guarantee that safety-critical tasks meet their deadlines. Conventional approaches rely on worst-case execution times (WCETs), which account for extremely rare pathological scenarios and consequently lead to significant over-provisioning of processor cores. This paper proposes a probabilistic schedulability analysis that exploits the statistical rarity of multiple vertices within a DAG exceeding their expected execution budgets. By grouping vertices within each DAG into small clusters and bounding the probability that more than one vertex in a cluster overruns, the method assigns each cluster a tighter execution budget than the sum of individual WCETs, thereby reducing the number of cores required. The clustering configuration is optimized via simulated annealing to minimize total core usage while maintaining a designer-specified bound on the system-level probability of deadline misses. Experiments on synthetic task sets demonstrate that the proposed method reduces the required number of cores by up to 36% compared to a deterministic baseline, with larger gains for DAGs exhibiting higher internal parallelism.

Keywords and phrases:
Mixed-Criticality Systems, DAG Tasks, Probabilistic Analysis, Federated Scheduling, Real-Time Systems
Copyright and License:
[Uncaptioned image] © Hiroto Takahashi, Atsushi Yano, and Takuya Azumi; licensed under Creative Commons License CC-BY 4.0
2012 ACM Subject Classification:
Computer systems organization → Real-time systems
Funding:
This work was supported by JST CREST Grant Number JPMJCR23M1 and JST FOREST Program Grant Number JPMJFR242G.
Supplementary Material:
Software  (ECRTS 2026 Artifact Evaluation approved artifact): https://doi.org/10.4230/DARTS.12.2.11
Editor:
Angeliki Kritikakou

1 Introduction

Real-time systems are essential to modern safety-critical applications, such as autonomous driving, avionics, and industrial robotics [11]. These systems are characterized by a tight interaction with the physical world, where the correctness of an operation depends not only on the logical result but also on the time at which that result is produced. Consequently, these systems demand an exceptionally high level of reliability and predictability, as a single timing failure can lead to catastrophic consequences. To enforce this high reliability, international safety standards, for instance, ISO 26262 for the automotive industry, provide a rigorous framework for development and validation. These standards often require system designers to demonstrate that the probability of timing failures, such as deadline misses, remains below a strictly defined, small threshold [10]. To provide such assurance, schedulability analysis, which mathematically proves that timing constraints are met with a required level of assurance ranging from deterministic guarantees to probabilistic bounds, is of paramount importance.

The software architecture of contemporary real-time systems, particularly in the autonomous driving domain, is growing in complexity. Applications are no longer simple, sequential programs but are composed of multiple concurrent functions with intricate data dependencies, often modeled as Directed Acyclic Graph (DAG) tasks to capture internal parallelism and precedence constraints [17]. Furthermore, to reduce size, weight, power, and cost, integrating functionalities of varying degrees of importance onto a common multiprocessor platform has become common practice. This integration leads to a Mixed-Criticality System (MCS), where safety-critical functions (e.g., collision avoidance) coexist with non-critical ones (e.g., infotainment) [18, 3]. The confluence of these characteristics of parallelism, mixed-criticality, and multiprocessor platforms presents a significant challenge. Ensuring the safety and reliability of these integrated systems requires a sophisticated and rigorous schedulability analysis specifically tailored for mixed-criticality DAG tasks on multiprocessors.

A fundamental challenge in conventional schedulability analysis lies in the reliance on the Worst-Case Execution Time (WCET) to model task behavior. WCET analysis tools aim to provide an absolute upper bound on the execution time of a task, but to provide this upper bound, these tools must account for a vast number of unlikely, pathological scenarios, such as worst-case cache behavior and pipeline hazards [19, 1]. This approach inevitably results in a highly pessimistic estimation of the required computational resources. Such pessimism in WCET-based analysis forces significant over-provisioning of hardware, leading to inefficient resource utilization and increased system cost. In response to this problem, a trend has emerged to incorporate probabilistic approaches into schedulability analysis to mitigate pessimism, for example, by using probabilistic WCETs (pWCETs) [8, 5, 2]. However, while these methods have shown promise for simpler models, such as sequential or sporadic tasks, their application to the more complex domain of mixed-criticality DAG tasks on multiprocessor systems remains largely unexplored. This gap stems from the need to account for (i) internal parallelism and precedence constraints and (ii) mixed-criticality mode changes, both of which complicate probabilistic bounding of concurrent overruns on multiprocessors.

Based on these challenges, this work investigates the following research questions.

  • ■

    RQ1 (Core demand reduction): Under a system-level bound on the probability of deadline misses of HI-criticality tasks over a bounded time horizon (e.g., one hour of operation), how much can the required number of processor cores be reduced compared to deterministic WCET-based analysis?

  • ■

    RQ2 (Sensitivity to failure budget): How does the permitted system-level failure probability, i.e., the probability that any HI-criticality task misses a deadline within the operational window, affect the required number of cores, and at what point does further relaxation yield diminishing returns?

  • ■

    RQ3 (Scalability): Can such a probabilistic analysis be performed at practical computational cost for large task sets and large DAGs?

To answer these questions, this paper proposes a probabilistic schedulability analysis for mixed-criticality DAG tasks on multiprocessor platforms. Instead of modeling each task by a single WCET, the proposed method assigns each vertex a LO-level budget, i.e., a nominal execution-time budget expected to be met in typical runs, and a small probability of exceeding that budget (an overrun). Conventional deterministic analysis is pessimistic because such analysis effectively assumes that many vertices exceed their budgets at the same time, an event that is extremely rare in practice. In contrast, the proposed analysis exploits the rarity of multiple simultaneous overruns to reduce the required resources, while ensuring a designer-specified bound on the probability of deadline misses of HI-criticality tasks over the time horizon. The analysis adopts federated scheduling, which isolates high-utilization DAGs on dedicated cores, eliminating inter-task interference and making the per-task analysis tractable. Within each DAG, vertices are aggregated into small connected groups; because simultaneous overruns of multiple vertices in the same group are rare, each group can be assigned a tighter execution-time bound than the sum of individual WCETs. Each group is collapsed into one vertex to form a reduced DAG, enabling existing response-time bounds.

The contributions of this paper, which address RQ1–RQ3, are as follows:

  • ■

    Probabilistic analysis framework (RQ1): A probabilistic schedulability analysis for mixed-criticality DAG tasks under federated scheduling that reduces required cores while maintaining a system-level failure guarantee, combining (i) probabilistic vertex grouping and (ii) existing response-time bounds on the reduced DAG.

  • ■

    Optimization for resource efficiency (RQ1, RQ2): A grouping optimization formulation and a simulated-annealing-based search procedure that minimizes required cores while satisfying per-cluster failure constraints, enabling quantitative evaluation of how the system-level failure budget affects resource demand.

  • ■

    Evaluation of effectiveness and scalability (RQ1, RQ2, RQ3): An evaluation comparing against deterministic baselines, characterizing strengths and limitations across task settings, and reporting computational scalability across task-set and DAG sizes.

The remainder of this paper is structured as follows. Section 2 defines the system model, including the mixed-criticality DAG task model and the probabilistic execution model. Section 3 presents the task classification scheme and design policy. Section 4 describes the probabilistic clustering scheme and multipath-based response time analysis. Section 5 details the simulated annealing optimization algorithm. Section 6 provides an experimental evaluation comparing the proposed method against existing approaches. Section 7 surveys related work in mixed-criticality scheduling and probabilistic timing analysis. Finally, Section 8 concludes the paper and outlines directions for future research.

2 System Model

Figure 1: Overview of the system model and probabilistic execution model.

The formal models and assumptions used throughout this paper are detailed below. The platform and the structure of the mixed-criticality parallel tasks are defined first. Subsequently, the probabilistic execution model that forms the basis of the schedulability analysis is introduced. An overview of the system model is illustrated in Figure 1. A summary of the symbols used to define the system is provided in Table 1.

Table 1: Summary of notation.
Symbol Description
N The number of tasks in the system.
τ A task set {τ1,…,τN}.
τi The i-th task in the task set.
Gi The DAG structure (Vi,Ei) of task τi.
Vi,Ei Sets of vertices and edges in Gi.
Ti The minimum inter-arrival time (period) of task τi.
Di The relative deadline of task τi.
χi The criticality level of task τi∈{LO,HI}.
CiL,CiH The LO-level and HI-level total work of task τi.
cvL,cvH The LO-level and HI-level execution-time budgets of vertex v.
LiL,LiH The LO-level and HI-level critical-path length of task τi.
L⁢(G) Critical-path length (longest source-to-sink path) of DAG G.
vol⁢(G) Total work (sum of all vertex execution times) of DAG G.
FS The system-wide permitted failure probability (per operational window).
W Operational window length used to interpret FS (e.g., one hour).
fvjob Per-job probability that vertex v of a HI-criticality task exceeds cvL.
gmjob Per-job cluster-failure probability for cluster m (two or more vertices exceed cvL).
gmW Window-W cluster-failure probability for cluster m.
ni⁢(W) Safe upper bound on the number of jobs of τi overlapping window W.
p Number of processors (cores) allocated to a DAG.
pi∗ Minimum number of cores for task τi to meet its deadline Di.
now⁢() Current wall-clock time, measured using a monotonic clock.
rand⁢() A pseudo-random number drawn independently from a uniform distribution over [0,1], generated using a fixed seed.

2.1 Platform and Task Model

This work considers a dual-criticality model, where each task is assigned one of two criticality levels: LO (low) or HI (high). The system under consideration is a set of N independent, sporadic mixed-criticality DAG tasks, denoted by τ={τ1,τ2,…,τN}, scheduled on a multiprocessor platform with identical cores. Each task τi generates a potentially infinite sequence of jobs. Each task τi is characterized by the tuple (Gi,Ti,Di,χi), where Gi=(Vi,Ei) is a DAG with vertices Vi representing sequential subtasks and edges Ei representing precedence constraints, Ti∈ℝ+ is the minimum inter-arrival time (period), Di=Ti is the relative deadline (implicit-deadline model), and χi∈{LO,HI} denotes the task criticality.

The execution behavior is specified by the work Ci (sum of vertex execution times) and span Li (critical-path length). In the mixed-criticality setting, both are given at LO and HI levels: CiL≤CiH and LiL≤LiH.

For a HI-criticality task τi (χi=HI), both LO-level (CiL,LiL) and HI-level (CiH,LiH) parameters are specified. For a LO-criticality task τi (χi=LO), only the LO-level parameters (CiL,LiL) are defined. The system begins in a LO-mode, where all vertices of HI-criticality tasks are expected to complete within their LO-level execution budgets cvL. If any vertex of a HI-criticality task exceeds its LO-level budget cvL, the system transitions to a HI-mode. Note that such a mode transition triggered by a single vertex exceeding cvL is an expected operational event and is provisioned by the cluster execution budget. The probabilistic failure budget FS is reserved exclusively for violations of the Single-HI Assumption, i.e., the rarer event in which two or more vertices within the same cluster exceed their LO-level budgets in the same job, as formalized in Section 4.

Throughout this paper, vertex-level probabilistic execution parameters are treated as the primary input to the analysis. Specifically, each vertex v∈Vi is associated with LO- and HI-level execution-time parameters, cvL and cvH, and a per-job exceedance probability defined at the vertex level, formalized below. Task-level work parameters are used as aggregate quantities derived from these vertex-level parameters; in particular, CiL=∑v∈VicvL and CiH=∑v∈VicvH when CiH is defined.

2.2 Probabilistic Execution Model

To mitigate the pessimism of traditional WCET-based analysis, this work adopts a two-point budget model with exceedance probability. Rather than requiring a full probabilistic WCET (pWCET) distribution, this model uses only exceedance probabilities at specified budget thresholds. For HI-criticality tasks, each vertex v is characterized by:

  • ■

    A LO-level budget (threshold) cvL.

  • ■

    A HI-level budget cvH (cvH≥cvL), representing a high-confidence upper bound for rare scenarios.

  • ■

    A per-job exceedance probability fvjob≜Pr⁡[Xv>cvL], where Xv denotes the actual execution time of vertex v in a job.

  • ■

    A deterministic upper-bound guarantee: Xv≤cvH almost surely. That is, cvH is a safe upper bound that the actual execution time never exceeds, ensuring that a vertex whose LO-level budget is exceeded still completes within cvH.

For LO-criticality tasks, only the LO-level budget cvL is defined for each vertex; the HI-level budget cvH and the exceedance probability fvjob are not applicable. This model captures the essential probabilistic behavior needed in the analysis without requiring a full execution-time distribution. The parameters cvL, cvH, and fvjob are treated as input derived from timing analysis or measurement campaigns (e.g., by selecting budgets at desired confidence levels). The value of fvjob is assumed to be small, reflecting the rarity of worst-case execution scenarios.

Execution-time samples of different vertices are assumed to be independent. This assumption enables computation of joint overrun probabilities; potential correlations (e.g., shared caches) are left for future work.

A system-wide permitted failure probability, FS, is specified for an operational window of length W (e.g., one hour). To relate the per-job exceedance probability to the system-level budget defined over window W, the probability that an exceedance occurs in any job whose execution can overlap with the window is conservatively upper-bounded. Let ni⁢(W) be an upper bound on the number of jobs of task τi whose execution can overlap with an operational window of length W. Under the sporadic task model with implicit deadlines (Di=Ti), assuming that each job either completes or is aborted by its deadline, a safe bound is

ni⁢(W)≜⌊WTi⌋+2. (1)

This bound accounts for up to ⌊W/Ti⌋ full periods inside the window, plus at most one job released just before the window start and one job released near the window end, whose execution (or deadline) can still fall within the window. All jobs whose execution can overlap with the window are conservatively counted; for implicit deadlines (Di=Ti), this also upper-bounds the number of jobs whose deadlines can fall within the window. Let {1,…,ni⁢(W)} index the set of jobs of τi whose executions can overlap with the window. All random variables and events in this paper are defined on an underlying probability space (Ω,ℱ,Pr), where Ω is the sample space, ℱ is the event space, and Pr is the probability measure. Let Ov,k∈ℱ denote the event that vertex v in the k-th job exceeds cvL, i.e., Ov,k≜{ω∈Ω:Xv,k⁢(ω)>cvL}, where Xv,k is the random variable representing the actual execution time of vertex v in the k-th job. Then, by the union bound, the window-W exceedance probability fvW satisfies

fvW≜Pr⁡[⋃k=1ni⁢(W)Ov,k]≤min⁡{1,ni⁢(W)⁢fvjob}. (2)

If exceedance events were independent across jobs, the exact conversion would be 1−(1−fvjob)ni⁢(W), which is well approximated by ni⁢(W)⁢fvjob when fvjob is small.

Throughout this paper, the superscript “job” denotes per-job quantities, while the superscript “W” denotes window-W quantities. This distinction is critical: cluster-failure analysis is performed at the per-job level, then converted to window-W for comparison with the system-level budget FS.

The events of different vertices exceeding their LO-level budgets are assumed to be statistically independent. This assumption allows for the calculation of the joint probability of multiple vertices overrunning their LO-level budgets simultaneously.

2.3 Scheduling Objective

The objective of this work is to develop a schedulability analysis that provides a probabilistic guarantee for HI-criticality tasks. The proposed analysis later groups vertices of a high-utilization HI-criticality DAG into clusters; informally, a cluster failure denotes the event that two or more vertices in the same cluster exceed their LO-level budgets in the same DAG job. A task set is deemed probabilistically schedulable if the following conditions are met:

  1. 1.

    In the LO-mode (i.e., no vertex of any HI-criticality task exceeds its cvL), all jobs of all tasks must meet their deadlines.

  2. 2.

    In the HI-mode, all jobs of HI-criticality tasks must meet their deadlines, provided that no cluster failure (Definition 3) occurs.

  3. 3.

    The probability that a cluster failure (Definition 3) occurs for any high-utilization HI-criticality DAG within the operational window W must not exceed the system-level permitted failure probability, FS.

  4. 4.

    LO-criticality tasks are not guaranteed in HI-mode; whether they are dropped or served best-effort is implementation-dependent.

The probabilistic analysis (clustering and window-level budgeting) applies only to high-utilization HI-criticality DAGs, reducing resource overhead compared to deterministic WCET-based provisioning.

3 Task Classification and Overview

The proposed probabilistic schedulability analysis framework is presented below. The key insight is that conventional mixed-criticality analysis tends to be overly pessimistic. Deterministic approaches treat the LO-mode and HI-mode separately and assume that, once the system enters HI-mode, every HI-criticality task could simultaneously require execution up to its HI-level WCET. In practice, however, the probability that any single task exceeds its LO-level budget is already very small, so requiring resources for the simultaneous worst-case execution of all HI-criticality tasks leads to significant over-provisioning. By leveraging the system-level permitted failure probability FS defined over an operational window of length W (e.g., one hour), the proposed method rules out such extremely rare scenarios and reduces the required number of processor cores.

Throughout this section, implicit-deadline sporadic DAG tasks are considered, where Di=Ti for all tasks τi. The proposed method follows the federated scheduling paradigm [15], which partitions tasks based on their resource requirements.

Definition 1 (High-Utilization Task).

A DAG task τi is classified as a high-utilization task if uiH=CiH/Ti>1, where CiH=∑v∈VicvH is the sum of the HI-level execution times of all vertices in DAG τi. Otherwise, τi is a low-utilization task.

Similarly, define the LO-level utilization as uiL≜CiL/Ti, where CiL=∑v∈VicvL is the sum of the LO-level execution times of all vertices in DAG τi. For LO-criticality tasks without HI-level parameters, uiL is used for utilization-based classification.

Intuitively, a high-utilization DAG cannot complete within its deadline on a single processor even under ideal work-conserving execution; thus, such a DAG requires multiple dedicated processors. Low-utilization tasks satisfy uiH≤1 and can be handled using partitioned scheduling as sequential tasks.

The proposed framework consists of the following components. For high-utilization DAG tasks, vertices are grouped into small clusters. Because simultaneous overruns of multiple vertices within the same cluster are statistically rare, each cluster can be assigned a combined execution budget smaller than the sum of individual HI-level budgets, reducing the total work that must be provisioned and lowering the required number of cores. A response-time bound is then computed on the reduced DAG in which each cluster is contracted into a single vertex. For low-utilization tasks, each DAG is conservatively abstracted as a sequential sporadic task with execution time equal to its total work Ci, enabling reuse of MC-Partition [12] for this subset. MC-Partition receives (CiL,CiH,Ti=Di) for HI-critical tasks and (CiL,Ti=Di) for LO-critical tasks (HI-level parameters are not defined for LO-critical tasks). Because MC-Partition guarantees schedulability using the HI-level execution times, low-utilization tasks always meet their deadlines regardless of whether any overrun occurs; thus, these tasks do not consume the probabilistic failure budget. The system-level failure budget FS is therefore enforced only for the probabilistic analysis of high-utilization HI-criticality DAGs.

The proposed method differs from prior federated mixed-criticality analyses [16, 14] in that the proposed clustering optimization exploits the statistical rarity of concurrent overruns to improve resource efficiency, rather than relying exclusively on deterministic HI-level execution budgets. The analysis pipeline proceeds as follows: tasks are first classified into high- and low-utilization subsets using Definition 1; for each high-utilization DAG, a clustering configuration is determined and the original DAG is reduced accordingly, and the required number of dedicated cores is computed via the multipath bound on the reduced DAG; in parallel, low-utilization tasks are assigned to remaining cores using partitioned scheduling with deterministic analysis. A task set is deemed probabilistically schedulable if both the deterministic conditions (for low-utilization tasks) and the probabilistic conditions (for the clustering-based high-utilization analysis under budget FS) are satisfied.

4 Probabilistic DAG Clustering

The probabilistic clustering scheme, which is the core contribution of this work, is described below. The goal is to reduce the pessimism in schedulability analysis by exploiting the statistical rarity of multiple vertices exceeding their LO-level execution budgets.

4.1 Assumptions and Definitions

The analysis relies on the following assumptions:

  1. 1.

    Per-vertex exceedance probability. Each vertex v in a DAG has an associated per-job exceedance probability fvjob, which represents the probability that the execution time of v exceeds its LO-level budget cvL. This quantity follows the definition given in Section 2.

  2. 2.

    Independence between vertices. Execution-time exceedance events of different vertices are assumed statistically independent, conditioned on the system mode. This assumption is adopted as a tractable modeling choice to compute joint overrun probabilities. Potential correlations within a DAG are not explicitly modeled in this paper.

  3. 3.

    Operational window for system-level budget. The system-wide permitted failure probability FS is defined over an operational window of length W (e.g., one hour), as specified in Section 2. For each vertex v, the probability that v exceeds cvL at least once within window W is conservatively bounded using the conversion in Equation 2.

A cluster is a subset of vertices in a DAG that satisfies the following properties:

  1. 1.

    Connectivity: The vertices in the cluster form a connected subgraph when edge directions are ignored.

  2. 2.

    Acyclicity preservation: The clustering configuration must be such that contracting each cluster into a single vertex does not introduce a cycle in the resulting graph.

  3. 3.

    Single-HI Assumption: For each vertex v in the cluster, at most one vertex is assumed to exceed its LO-level budget cvL and require its HI-level execution time cvH; all other vertices complete within their respective LO-level budgets. Conventional analysis provisions resources assuming that every vertex could overrun simultaneously. By designing the cluster execution budget to accommodate the case where exactly one vertex overruns, the analysis can handle single overruns without treating them as failures; only when two or more vertices overrun does the assumption break, and such events have negligibly small probability. This is an analysis-level budgeting assumption; violations are not ruled out, but are treated as cluster failures and accounted for probabilistically.

Definition 2 (Cluster Execution Time).

This definition is applied only to clusters formed within HI-criticality (high-utilization) DAGs, where both cvL and cvH are defined for every vertex v in the cluster. For a cluster containing vertices {v1,v2,…,vk}, the cluster execution time under the Single-HI Assumption is:

Ccluster=∑j=1kcvjL+maxj∈{1,…,k}⁡(cvjH−cvjL). (3)

The first term represents the baseline execution if all vertices take their LO-level budgets. The second term adds the maximum additional cost incurred when exactly one vertex takes its HI-level budget. This formulation provides a safe upper bound on the actual execution time, provided that the Single-HI Assumption holds.

As noted in Section 2, a single vertex exceeding its LO-level budget triggers a mode transition and is accounted for by the cluster execution budget Ccluster (Definition 2), which provisions for exactly one such overrun. A cluster failure occurs only when the Single-HI Assumption is violated, i.e., when two or more vertices in a cluster exceed their LO-level budgets during the same DAG job:

Definition 3 (Cluster Failure Event).

Let Vm denote the set of vertices in cluster m. For a fixed DAG job, let Xv denote the execution-time random variable of vertex v in that job. The cluster failure event failm∈ℱ is defined as

failm≜{ω∈Ω:|{v∈Vm:Xv⁢(ω)>cvL}|≥2}. (4)

Under the independence assumption in Section 4.1, the per-job cluster-failure probability gmjob≜Pr⁡[failm] is computed as follows.

Theorem 4 (Per-Job Cluster Failure Probability).

Consider a cluster m with vertices Vm={v1,…,vk} and per-job exceedance probabilities {fv1job,…,fvkjob}. The per-job cluster-failure probability is

gmjob=1−∏j=1k(1−fvjjob)−∑i=1k(fvijob⁢∏j≠i(1−fvjjob)). (5)

Proof.

Let Nexc≜|{v∈Vm:Xv>cvL}| denote the number of vertices that exceed their LO-level budgets in the fixed DAG job. The events {Nexc=0}, {Nexc=1}, and {Nexc≥2} form a partition. By the independence assumption, Pr⁡[Nexc=0]=∏j=1k(1−fvjjob) and Pr⁡[Nexc=1]=∑i=1kfvijob⁢∏j≠i(1−fvjjob). Since gmjob=Pr⁡[Nexc≥2]=1−Pr⁡[Nexc=0]−Pr⁡[Nexc=1], the result follows. ◀

This computation assumes independence of vertex exceedance events as stated in Section 4.1. Under positive correlation (e.g., due to shared-resource contention), the actual cluster-failure probability may exceed the value given by (5); incorporating such correlations conservatively is left for future work. Note that the system-level union bound (presented below in Theorem 7) remains valid regardless of inter-cluster correlation, since it only requires ∑mgmW<FS.

To relate the per-job cluster failure probability to the system-level budget over window W, the window-W cluster failure probability is defined as follows. Let τi be the task containing cluster m. Then:

gmW≜Pr⁡[cluster ⁢m⁢ fails at least once in window ⁢W]≤min⁡{1,ni⁢(W)⋅gmjob}, (6)

where ni⁢(W) is an upper bound on the number of jobs of τi whose execution can overlap with window W, as defined in Equation (1).

4.2 System-Level Probabilistic Guarantee

The central theorem connects per-cluster failure constraints to the system-level deadline miss probability. Here, FS is the permitted probability that any HI-criticality task misses a deadline within the operational window W (e.g., one hour). Given the system-level failure budget FS, this paper distributes it uniformly across the K clusters: each cluster m must satisfy gmW<FS/K. This choice is sufficient for the union bound (∑mgmW<FS) and avoids expanding the search space with per-cluster budget variables. Other allocation policies (e.g., risk-proportional allocation) are possible but are not considered in this paper.

After clustering, the original DAG is transformed into a reduced DAG where each cluster is collapsed into a single representative vertex. This reduction is necessary because the next response-time analysis (multipath bound) considers disjoint path sets; if a cluster were to span multiple such paths, the workload distribution would depend on which vertex in the cluster overruns, making the bound ill-defined. By contracting each cluster into a single vertex, the cluster execution time becomes a constant regardless of which internal vertex takes the HI-level budget, and existing DAG schedulability bounds can be applied directly.

Definition 5 (Reduced DAG).

Let G=(V,E) be a DAG with clustering 𝒞={C1,…,CQ}. The reduced DAG G′=(V′,E′) is defined by V′={v1′,…,vQ′}, where vm′ represents cluster Cm with execution time Ccluster⁢(Cm) from Equation 3, and E′={(va′,vb′)∣a≠b,∃u∈Ca,w∈Cb⁢ s.t. ⁢(u,w)∈E}.

Acyclicity preservation (property 2 above) is verified by attempting a topological ordering (equivalently, cycle detection via DFS) of the reduced DAG.

In the reduced graph, each cluster is represented by a single vertex with weight Ccluster; accordingly, L⁢(G′) is computed as the longest weighted path in the reduced graph. This abstraction is conservative because any parallelism internal to a cluster is not exploited in the critical-path computation, so a cluster may contribute more to L⁢(G′) than its internal span would suggest. This abstraction is adopted to obtain a compositional vertex-level execution bound that can be passed directly to existing DAG response-time bounds. The loss of internal parallelism is limited when clusters are small or mostly follow precedence chains; conversely, large internally parallel clusters can increase L⁢(G′), making them generally less favorable from the perspective of the response-time bound.

Definition 6 (Valid Clustering).

A clustering configuration 𝒞={C1,…,CK} is valid if every cluster forms a connected subgraph (ignoring edge directions) and the graph obtained by contracting each cluster into a single vertex (Definition 5) remains acyclic.

The theorem relies on three conditions: (i) high-utilization DAGs are scheduled under federated scheduling with dedicated cores, eliminating inter-task interference; (ii) low-utilization tasks are scheduled on separate cores using deterministic WCET analysis and do not contribute to the probabilistic failure budget; (iii) the execution time of each cluster is bounded by Ccluster (Definition 2) whenever the Single-HI Assumption holds.

Theorem 7 (System-Level Guarantee).

Let 𝒞={C1,…,CK} be a valid clustering configuration (Definition 6) for all high-utilization HI-criticality DAGs, where K is the total number of clusters. If:

  1. 1.

    Each cluster m satisfies gmW<FS/K, and

  2. 2.

    For each high-utilization HI-criticality task τi, the multipath response-time bound (defined in Section 4.3) on its reduced graph satisfies Ri≤Di,

then the probability of any HI-criticality deadline miss within the operational window W is at most FS.

Proof.

A deadline miss can occur only if the Single-HI Assumption is violated for some cluster (i.e., failm occurs for some m), causing the cluster execution time to exceed Ccluster. By the union bound:

Pr⁡[⋃m=1K{cluster ⁢m⁢ fails in window ⁢W}]≤∑m=1KgmW<∑m=1KFSK=FS. (7)

If no cluster failure occurs (probability >1−FS), then each cluster completes within Ccluster, and condition (2) ensures that the reduced DAG meets its deadline. The union bound requires no independence between clusters. ◀

Intuitively, the guarantee is constructed in three stages. First, Theorem 4 quantifies the risk within a single cluster: given the per-vertex exceedance probabilities, the probability that two or more vertices in the same cluster simultaneously exceed their LO-level budgets in a single job is computed exactly. This per-job probability gmjob is typically very small because the exceedance probabilities fvjob themselves are small and gmjob is dominated by the product of two such quantities. Second, the per-job probability is scaled to the operational window via (6), yielding gmW, which accounts for the fact that a cluster is exercised once per job release across the entire window. Finally, the union bound aggregates the per-cluster window probabilities into a system-level guarantee without assuming independence between clusters: even in the worst case where cluster failures are perfectly correlated, the bound ∑mgmW<FS ensures that the total probability remains below the permitted threshold. Each stage narrows the scope of the probabilistic argument, from individual vertices, to clusters, to the system, so that the final guarantee is both composable and conservative.

Design trade-off.

The clustering configuration involves a three-way trade-off among resource savings, failure probability, and DAG structure. Merging vertices into larger clusters reduces the total number of clusters K, which relaxes the per-cluster constraint gmW<FS/K; at the same time, adding vertices to a cluster increases the cluster-failure probability gmjob because more vertices can jointly overrun. The resource benefit arises because the cluster execution time Ccluster (Definition 2) is no larger than the sum of individual HI-level budgets ∑cvH and, under the Single-HI Assumption, typically smaller when the cluster contains two or more vertices, reducing the total work vol⁢(G′) of the reduced DAG and thereby lowering the multipath-based core requirement pi∗. The critical-path length of the reduced DAG is less sensitive to clustering because precedence-connected vertices often contribute similar span whether or not they are merged; the optimization later uses a path-length tie-breaker to discourage excessive span increases. Two layers of conservatism ensure soundness: the per-job to window-W conversion via the union bound (Eq. (6)), and the system-level union bound over all clusters (Theorem 7). Finally, the singleton clustering (each vertex in its own cluster) always satisfies gmjob=0 and is therefore trivially feasible; this guarantees that a feasible solution exists at the start of the optimization and that the search can only improve upon the deterministic (singleton) baseline.

4.3 Response Time Bound

Once the reduced DAG is constructed, the minimum number of processor cores required to meet the deadline is computed using the multipath bound [9]. The response-time bounds in this subsection assume a set of p identical cores executing the vertices of a single DAG G under a work-conserving scheduler. A vertex v is eligible when all its predecessors in G have completed execution, and a work-conserving scheduler never leaves a core idle while an eligible vertex exists. No further restriction is placed on the scheduling policy: the bounds hold regardless of whether preemption or migration is permitted. Within each DAG job, every vertex becomes eligible solely through precedence completion; in particular, there is no release jitter among the vertices of a single job. Under federated scheduling, each high-utilization DAG is allocated dedicated cores, so inter-task interference does not arise and these per-DAG assumptions are sufficient.

The classical response-time bound for executing a DAG G on p identical cores under these assumptions is given by Graham [6]:

R≤L⁢(G)+vol⁢(G)−L⁢(G)p (8)

where L⁢(G) denotes the critical-path length (the longest path from any source vertex to any sink vertex) and vol⁢(G) is the total work (sum of execution times of all vertices). Intuitively, the first term accounts for the serial bottleneck imposed by the critical path, while the second term distributes the remaining work across p processors. This bound is pessimistic because the formulation captures only a single critical path and ignores the additional parallelism contributed by multiple disjoint long paths. The multipath bound exploits multiple long paths to derive a tighter estimate.

Definition 8 (Generalized Path List).

A generalized path list (λ0,…,λk) is a set of k+1 vertex-disjoint sequences where each λi=(u0,…,un) satisfies that uj is an ancestor of uj+1 for all j.

Theorem 9 (Multipath Bound [9]).

Given a generalized path list (λi)i=0k with k∈[0,p−1], the response time R of DAG G on p identical cores under any work-conserving scheduler satisfies:

R≤minj∈[0,k](L(G)+vol⁢(G)−∑i=0jw⁢(λi)p−j)=:Rmultipath(G,p), (9)

where w⁢(λi) denotes the total execution time of all vertices in path λi, and the minimum is taken over the optimal generalized path list for the given p.

The optimal generalized path list is computed by reducing the problem to a minimum-cost flow problem [9], with time complexity O⁢(p⁢(|V′|2+|V′|⁢log⁡|V′|)).

▶ Remark 10 (Monotonicity).

For a fixed DAG G, the bound Rmultipath⁢(G,p) is non-increasing in p. This holds because adding a core can only reduce each term (vol⁢(G)−∑w⁢(λi))/(p−j) and can additionally enlarge the feasible set of generalized path lists (since k≤p−1). Consequently, the minimum core count pi∗ defined below can be computed by binary search.

Minimum Core Computation.

For a reduced DAG Gi′ of task τi, the minimum number of dedicated cores is:

pi∗=min⁡{p∈ℕ∣Rmultipath⁢(Gi′,p)≤Di} (10)

computed via binary search over p∈[1,pmax]. The monotonicity established in Remark 10 guarantees that if Rmultipath⁢(Gi′,p)≤Di holds for some p, then it also holds for every p′>p, making binary search applicable.

5 Clustering Optimization

Algorithm 1 Probabilistic Clustering Optimization.

The clustering problem entails a large combinatorial search space, because a clustering configuration simultaneously affects (i) the reduced DAG structure (and its acyclicity), (ii) the multipath-based core requirement pi∗, and (iii) the probabilistic constraint gmW<FS/K. In particular, merge and split transitions change the total number of clusters K, thereby shifting the per-cluster budget FS/K for all clusters simultaneously; this global coupling means that a local transition can alter the feasibility of many other clusters, making the search space highly non-smooth and challenging for purely local or greedy optimization. Moreover, the pipeline from a clustering assignment to the required number of cores involves multiple coupled stages, constructing the reduced DAG, computing the multipath response-time bound, and evaluating the probabilistic constraint, each of which is non-trivial. Because this pipeline has no closed-form relationship between the clustering decision variables and the objective, exact optimization methods (e.g., integer programming or dynamic programming) cannot be directly applied. This work therefore adopts simulated annealing (SA), a metaheuristic for exploring rugged discrete search spaces [13, 4]. Although SA does not guarantee a globally optimal solution, the objective function in (11) changes smoothly under local transitions (moving a vertex or merging two small clusters typically changes the core count by a small integer), which allows SA to converge to a good local optimum within a practical time budget.

Simulated annealing is a randomized local-search method. At each step, the algorithm samples a neighboring solution and accepts the candidate either when the candidate improves the objective or, otherwise, with a probability controlled by a temperature parameter. This design enables occasional acceptance of worse solutions early in the search to escape local minima, while the search becomes increasingly selective as the temperature decreases.

The optimization state is a clustering assignment for each high-utilization DAG. The initial state assigns each vertex to its own singleton cluster, which is always feasible since each gmW=0 (no two vertices can fail in a single-vertex cluster). At each iteration, the algorithm selects one high-utilization DAG and generates a candidate by applying one of the following neighborhood transitions (illustrated in Figure 2):

  • ■

    Move: Move a vertex to a neighboring cluster.

  • ■

    Merge: Merge two adjacent clusters.

  • ■

    Split: Split a cluster into two connected subclusters.

  • ■

    Merge-Split: This joint transition is useful for repartitioning adjacent clusters: a Split-only move often worsens the objective as an intermediate step, whereas Merge-Split can directly propose a new boundary between two neighboring clusters. Specifically, it merges two adjacent clusters into one, then splits the merged cluster into two connected subclusters and adopts the split that yields the best objective value. If the merged cluster contains at most kmax vertices (a configurable threshold), all valid connected bipartitions are enumerated exhaustively and the best one is selected. If the merged cluster exceeds kmax vertices, a fixed number of random connected bipartitions are sampled instead, avoiding the exponential enumeration cost.

If the resulting reduced DAG is cyclic, the candidate is rejected immediately.

Figure 2: The four neighborhood transitions used in simulated annealing. Each colored rectangle represents a distinct cluster.

The optimization minimizes a weighted combination of three terms: (1) the total number of required cores Ecores=∑ipi∗, (2) a tie-breaker term Epath=∑iL⁢(Gi′) based on the critical-path length of the reduced DAG, and (3) a penalty term Pviol that penalizes constraint violations; specifically, Pviol=∑mmax⁡(0,gmW−FS/K) accumulates the excess failure probability over all clusters that violate the per-cluster budget. Since low-utilization tasks are partitioned independently using MC-Partition, their core allocation is fixed and not affected by clustering; hence the optimization minimizes only the high-utilization core sum ∑ipi∗. The combined objective is

E=Ecores+ε⋅Epath+ω⁢(t)⋅Pviol, (11)

where ε is a small constant (e.g., 10−4) so that Epath serves only as a tie-breaker. The penalty weight ω⁢(t) increases linearly over the optimization time budget, from ωstart to ωend, to shift the search gradually from exploration to constraint satisfaction.

Let Δ⁢E=Ecandidate−Ecurrent be the objective difference. SA accepts any improving move (Δ⁢E<0) unconditionally, and accepts a worsening move (Δ⁢E>0) with probability exp⁡(−Δ⁢E/T⁢(t)), where T⁢(t) is the temperature at time t. Intuitively, when Δ⁢E=1 and T⁢(t)=1, the acceptance probability becomes exp⁡(−1)=1/e≈0.368; as T⁢(t) decreases, the same worsening move is less likely to be accepted. Improving moves (Δ⁢E<0) are always accepted.

This work uses an exponential cooling schedule, in which the temperature decreases geometrically from Tstart to Tend:

T⁢(t)=Tstart⁢(TendTstart)t/tlimit, (12)

where Tstart and Tend are user-specified initial and final temperatures that control the acceptance rate of worsening moves, and tlimit is the time budget. They are chosen relative to the scale of the objective function. Since Ecores is the dominant term and changes in integer units, the temperature is kept much smaller than the cost of increasing the required number of cores. However, Tstart is kept positive and large enough to accept small worsening moves in the auxiliary terms, especially the tie-breaker term ε⁢Epath, so that the search can explore different clusterings with the same core count and avoid purely greedy local decisions. As the temperature decreases toward Tend, the search gradually becomes more selective, so that late-stage iterations focus on local refinement rather than broad exploration.

Intermediate solutions can violate the probabilistic constraint, but the algorithm tracks the best feasible solution encountered. Only feasible solutions (all gmW<FS/K) are candidates for the final output. Let K denote the total number of clusters over all reduced DAGs of HI-criticality tasks; K is recomputed after each accepted merge or split. Since the singleton clustering is always feasible (each gmW=0), a feasible solution is guaranteed to exist; Algorithm 1 summarizes the optimization procedure.

Each SA iteration evaluates one clustering candidate. The dominant cost is the multipath bound computation for the affected DAG, which takes O⁢(pmax⁢(|V′|2+|V′|⁢log⁡|V′|)) time, where |V′| is the number of clusters in the reduced DAG. Recomputing gmW for affected clusters is proportional to the number of touched clusters and their sizes; a conservative bound is O⁢(K⋅kmax), where K is the number of clusters in the system and kmax is the maximum cluster size. With Niter SA iterations, the total time complexity is O⁢(Niter⋅pmax⋅|V|2) in the worst case. In practice, the time budget tlimit determines the number of iterations.

To reduce overhead, each transition affects only one DAG; the core counts of other DAGs are cached and reused. The per-job cluster failure probability gmjob is computed exactly using Theorem 4, then converted to gmW via Equation 6; no approximation is used other than the union bound. No explicit limit is placed on cluster size; the constraint gmW<FS/K implicitly limits how many vertices can be merged. Cycle detection is performed via DFS on the reduced DAG; if a back edge is found (indicating a cycle), the clustering is rejected.

6 Evaluation

The proposed probabilistic schedulability analysis is evaluated through experiments using synthetic task sets.

6.1 Experimental Setup

Compared Methods.

Three methods that differ in their response-time bound and use of probabilistic reduction are compared:

  • ■

    Fed-2018: The federated scheduling approach from Pathan [16]. For high-utilization tasks, this method computes dedicated cores using the standard work-span bound ⌈(Ci−Li)/(Di−Li)⌉ with HI-level parameters. Low-utilization tasks are partitioned using MC-Partition.

  • ■

    NoCluster: A baseline that applies the multipath schedulability bound [9] to high-utilization tasks, but without probabilistic clustering; all vertices use HI-level execution budgets. Low-utilization tasks use the same MC-Partition as Fed-2018.

  • ■

    Proposed: The proposed method combining probabilistic clustering with the multipath bound. Cluster assignments are optimized via simulated annealing under the system-level failure constraint.

Fed-2018 is included to assess the impact of the response-time bound (work-span vs. multipath), and NoCluster to isolate the effect of probabilistic clustering (NoCluster vs. Proposed).

DAG Generation.

Synthetic DAG tasks are generated using RD-Gen [20] with two structural configurations:

  • ■

    Fan-in: Fan-in/fan-out structures with edge density d∈[1.2,4.0].

  • ■

    Chain: Chain-based structures with main path length in [1,30] (log-spaced) and 0–10 sub-paths.

The number of vertices per DAG is sampled uniformly from [20,100].

Timing Parameters.

All timing parameters (cvH, cvL, Di, Ti) are expressed in milliseconds. The HI-level WCET of each vertex is sampled as cvH∼𝒰⁢[50,500] ms, and the LO-level WCET is set as cvL=cvH/4. For each HI-critical DAG, deadline tightness ρ∈[0.7,0.8] is sampled and the deadline is set as Di=LiH/ρ; for LO-critical DAGs, Di=LiL/ρ is used. Since ρ<1, Di>Li holds for all DAGs, ensuring the work-span bound is well-defined. All tasks use implicit deadlines, so the period is set as Ti=Di. These fixed choices are used to isolate the effects of DAG structure, failure budget, and optimization time, since varying all task-generation parameters simultaneously would require a much larger number of task sets to obtain stable trends. The setting cvL=cvH/4 creates a clear separation between typical and rare execution budgets, and ρ∈[0.7,0.8] provides a moderately stressed deadline range that is neither trivially loose nor almost infeasible. Different parameter values may affect the magnitude of the observed savings, although the mechanism of the proposed analysis remains the same; a broader sensitivity study over these parameters is left for future work.

Task Set Construction.

Each task set is constructed by selecting DAGs from pre-generated pools partitioned by Critical-Path Ratio (CPR) bins, where CPR=Li/Ci. DAGs are added until the total vertex count exceeds 1000. Total vertex count is used rather than task count to ensure statistically sufficient instance sizes and comparable computational load across methods, as all methods operate under the same per-task-set time budget. The HI:LO criticality ratio is fixed at 1:1.

Probabilistic Parameters.

The operational window is W=3.6×106 ms (one hour), and the system-level failure budget is FS=10−9 per window. The per-job vertex exceedance probability is fvjob=10−6. Because W and Ti share the same unit (ms), the job count ni⁢(W)=⌊W/Ti⌋+2 is computed directly. For each task set with K clusters, the per-cluster failure constraint is gmW<FS/K, ensuring that the union bound over all clusters satisfies the system-level guarantee. The evaluation focuses on guaranteeing HI-criticality tasks; LO-criticality tasks are not guaranteed in HI-mode and do not affect the probabilistic failure budget.

Optimization Configuration.

Simulated annealing uses exponential cooling from T=10−2 to 10−5 with a time budget of 1 second per task set. The penalty weight increases linearly from ω=0.5 to 5.0. The merge-split exhaustive enumeration threshold is kmax=12.

Environment.

All experiments run on AMD Ryzen 7 PRO 8840U (2.9 GHz, 8 cores) with 14 GiB RAM. For each CPR bin, n=100 task sets are generated. The primary metric is the total number of processor cores required for schedulability: the sum of dedicated cores (pi∗) for each high-utilization HI-criticality DAG, plus the cores used by MC-Partition for low-utilization tasks.

6.2 Impact of DAG Parallelism

(a) Fan-in DAGs.

(b) Chain DAGs.

Figure 3: Distribution of required cores across CPR (critical-path ratio) bins for (a) fan-in and (b) chain DAG structures. Each bin contains 100 task sets. Lower CPR indicates higher parallelism. Proposed, NoCluster, and Fed-2018 are compared.

The distribution of required cores across CPR bins for fan-in and chain DAG structures is shown in Figure 3. Lower CPR indicates higher parallelism (critical path is short relative to total work). Each bin contains n=100 task sets.

Fan-in DAGs (Figure 3(a)).

For fan-in structures, Proposed consistently requires fewer cores than both baselines. At CPR ∈[0.1,0.2), Fed-2018 requires a mean of approximately 118 cores, while Proposed achieves roughly 93, a reduction of about 21%. NoCluster provides intermediate improvement (mean ≈100), demonstrating that the multipath bound alone reduces pessimism, while probabilistic clustering provides additional gains.

Chain DAGs (Figure 3(b)).

For chain structures, the improvement is more pronounced. At CPR ∈[0.1,0.2), Proposed reduces mean cores by approximately 36% compared to Fed-2018 (mean: 140→90). As CPR increases, the gap narrows and all methods converge toward CPR ∈[0.6,0.7). This convergence is not because clustering becomes ineffective, but because all methods already achieve low core counts for near-sequential DAGs, approximately 50–70 cores for fan-in and 35–42 for chain, leaving little room for further reduction. When the critical path accounts for most of the total work, even the work-span bound produces a tight allocation, so the relative benefit of probabilistic clustering diminishes. At low CPR, chain DAGs also exhibit higher variance; Fed-2018 produces outliers exceeding 200 cores, whereas Proposed reduces both the mean and variance by absorbing rare overruns within each cluster.

6.3 Impact of System-Level Failure Budget

This subsection investigates how the system-level permitted failure probability FS affects the required number of cores. A separate set of 1000 task sets is generated with mixed fan-in and chain DAGs, each containing at least 1000 vertices. Deadline tightness is sampled as κ∈[1.3,1.5] with Di=Ti=⌈κ⋅LiH⌉, and all other parameters follow Section 6.1. Each task set is evaluated under three failure budgets FS∈{10−9,10−8,10−7} with the same clustering optimization, and the resulting core counts are compared pairwise.

Figure 4: Win/tie/loss comparison of required cores across FS pairs (n=1000 task sets each). For each pair x→y, “y-side better” means the more permissive FS (larger value) yields fewer cores.

Figure 4 summarizes the pairwise comparison for all three FS pairs. In the 10−9→10−7 pair, the more permissive budget yields fewer cores in 543 out of 1000 task sets, while 207 task sets require more cores and 250 are ties. The 10−9→10−8 pair shows a similar trend: 548 task sets benefit from the relaxed budget, with 200 worse and 252 ties. These results confirm that a larger FS expands the feasible region for clustering, allowing more vertices to share clusters without violating the per-cluster failure constraint gmW<FS/K, thereby reducing the total number of dedicated cores in the majority of cases.

In contrast, the 10−8→10−7 pair is dominated by ties: 565 task sets show no change, while only 199 improve and 236 are worse. This convergence occurs because, beyond a certain tolerance level, the clustering optimization reaches diminishing returns. When FS is already sufficiently large (e.g., 10−8), most clusters are well within the failure constraint, and the binding bottleneck shifts from the probabilistic budget to the structural properties of the DAG (e.g., critical-path length). Increasing FS further provides limited additional freedom for merging clusters, so the optimized clustering configurations under 10−8 and 10−7 tend to converge to similar solutions.

6.4 Impact of Optimization Time Budget

Figure 5: Comparison of required cores between 1-second and 10-second optimization budgets for the same 700 task sets. Points below the diagonal indicate that the 10-second budget yields fewer cores. Left: chain DAGs; right: fan-in DAGs.

This subsection investigates whether a longer optimization time budget improves solution quality. The same 700 task sets used in Section 6.2 are evaluated under two time budgets: 1 second and 10 seconds per task set, with all other parameters held constant. Figure 5 plots the required cores under the 1-second budget (horizontal axis) against the 10-second budget (vertical axis) for both chain and fan-in structures.

For chain DAGs, the majority of points lie below the diagonal, indicating that additional optimization time improves solution quality in most cases. The densest cluster appears at low core counts (20–30 cores at 1 s, 20–25 at 10 s), corresponding to high-CPR (near-sequential) task sets where the margin for improvement is small. For task sets in the mid-range (60–120 cores at 1 s), the 10-second budget typically reduces the core count by 10–30 cores, with the points spread widely below the diagonal. For fan-in DAGs, a similar pattern holds but with greater spread; the densest region is around (30–40, 25–35), and points at higher core counts (80–150 at 1 s) show reductions of up to 20–40 cores. In both structures, a small number of task sets lie on or near the diagonal, indicating that the 1-second budget already finds a near-optimal clustering for those instances.

Combined with the results from Section 6.2, where even a 1-second budget already outperforms the deterministic baselines Fed-2018 and NoCluster, these results show that the proposed method achieves immediate improvements in core efficiency and continues to converge toward lower core counts as more optimization time is allocated. This enables a practical trade-off between computation time and resource savings depending on system constraints.

7 Related Work

Prior work on mixed-criticality scheduling is reviewed below, focusing on three key areas relevant to this paper: probabilistic approaches for mixed-criticality systems, federated scheduling of mixed-criticality DAG tasks, and response-time analysis for DAG tasks. A comparative summary is provided in Table 2.

One line of research has focused on incorporating permitted system failure probabilities into the scheduling of mixed-criticality systems [8]. This approach introduces a probabilistic parameter for each high-criticality task, representing the likelihood of the task exceeding its typical execution time budget. Instead of pessimistically assuming that all high-criticality tasks might overrun simultaneously, the method groups tasks into clusters. For each cluster, a shared “server” capacity is provisioned to handle overruns from only one task at a time, under the condition that the probability of multiple simultaneous overruns is below the permitted system failure threshold. This strategy significantly reduces pessimism and improves resource efficiency. However, the analysis and scheduling technique are designed for sequential, independent tasks and do not address the challenges introduced by the internal parallelism and precedence constraints of DAG tasks.

Table 2: Comparison of features in related work.
Research Multiprocessor MCS Probabilistic DAG
TCAD 2022 [8] ✓ ✓ ✓
RTS 2021 [5] ✓ ✓ ✓
ECRTS 2018 [16] ✓ ✓ ✓
ISORC 2019 [14] ✓ ✓ ✓
RTSS 2024 [7] ✓ ✓ ✓
TCAD 2025 [9] ✓ ✓
This study ✓ ✓ ✓ ✓

Another relevant direction of research analyzes systems with probabilistic execution times and proposes metrics inspired by safety standards [5]. This work focuses on quantifying the impact of degradation, which occurs when lower-criticality tasks are dropped, on the overall system performance. Metrics such as the probability of a deadline miss per hour and the expected time before degradation are introduced to provide a more comprehensive view of system behavior. While this research provides a valuable framework for probabilistic analysis in mixed-criticality systems, the approach does not specifically consider the scheduling of parallel tasks with complex internal dependencies, such as those modeled by DAGs.

In the domain of mixed-criticality scheduling for parallel tasks, federated scheduling has been developed as an effective paradigm. Pathan [16] proposes a federated scheduling approach for mixed-criticality parallel tasks on multiprocessors, where high-utilization tasks are assigned dedicated cores and low-utilization tasks are scheduled on shared cores. The analysis provides a work-span bound to compute the number of dedicated cores for each high-utilization DAG. This method is used as a deterministic baseline (Fed-2018) in our evaluation. Li et al. [14] extend the federated scheduling idea to a semi-federated scheme, which allows partial core sharing among high-utilization DAGs to improve resource efficiency, while maintaining schedulability guarantees under mixed criticality. Guan et al. [7] address relaxed-deadline DAG tasks within a mixed-criticality context, providing the first federated schedulability analysis that handles the case where the deadline exceeds the period. While these approaches effectively manage parallel task scheduling under mixed criticality, they all rely on deterministic WCET parameters and do not exploit the statistical rarity of simultaneous overruns.

For response-time analysis of DAG tasks, He et al. [9] propose the multipath bound, which generalizes the classical work-span bound by exploiting multiple vertex-disjoint paths to derive a tighter response-time estimate. This bound is computed by reducing the problem to a minimum-cost flow formulation. The multipath bound is not specific to mixed-criticality systems and does not incorporate probabilistic execution models, but the multipath bound serves as the response-time analysis component in the proposed method.

The research presented in this paper bridges the gap between probabilistic mixed-criticality analysis and DAG task scheduling. By integrating probabilistic vertex grouping into the federated scheduling framework and applying the multipath bound on the resulting reduced DAGs, the proposed method addresses all four dimensions in Table 2, enabling resource-efficient scheduling with quantitative safety guarantees for mixed-criticality DAG tasks on multiprocessors.

8 Conclusion

This paper presented a probabilistic schedulability analysis for mixed-criticality sporadic DAG tasks on identical multiprocessors under federated scheduling. The key idea is to reduce the pessimism of WCET-based analysis by exploiting the statistical rarity of concurrent execution-time overruns. To this end, a probabilistic clustering scheme that bounds cluster execution under a Single-HI assumption and quantifies the probability that the assumption is violated is proposed. By converting per-job cluster-failure probabilities to an operational-window level and enforcing uniform per-cluster constraints, the analysis composes to a system-level failure guarantee through a union bound. This probabilistic constraint is then combined with a multipath-based response-time bound on the reduced DAG to compute the dedicated cores required for high-utilization tasks, and a simulated-annealing-based procedure is introduced to search for efficient clusterings under a fixed time budget.

Experimental results on synthetic DAG task sets indicate that the proposed method reduces the total required cores compared to deterministic baselines, and that probabilistic clustering yields additional gains beyond those obtained from switching from a work-span bound to a multipath bound alone, especially for DAGs with high parallelism. The sensitivity analysis further shows that, in our experiments, relaxing the system-level failure budget FS generally reduces the required number of cores; however, the marginal benefit diminishes as FS increases, suggesting a diminishing-returns regime where further relaxation yields only limited additional resource savings. The optimization time-budget study confirms that even a one-second search already outperforms the deterministic baselines, while extending the budget to ten seconds yields further reductions, particularly for task sets with moderate-to-high core demands. These results support the premise that incorporating probabilistic execution information into mixed-criticality federated analysis can improve resource efficiency while preserving a system-level failure budget.

Multiple directions remain for future work. First, the current formulation assumes independence of vertex exceedance events and uses a uniform failure-budget allocation across clusters; incorporating correlation models and exploring risk-proportional allocations could further improve tightness. Second, extending the analysis to constrained-deadline or arbitrary-deadline DAG models is an important next step. Finally, broader sensitivity studies over probabilistic parameters and more extensive scalability characterization will strengthen practical applicability.

References

  • [1] Jaume Abella, Damien Hardy, Isabelle Puaut, Eduardo Quiñones, and Francisco J. Cazorla. WCET analysis of parallel applications on multicore processors: A survey. IEEE Transactions on Computers, 64(10):2733–2748, 2015.
  • [2] Sergey Bozhko, Filip Marković, Georg von der Brüggen, and Björn B. Brandenburg. What really is pWCET? a rigorous axiomatic proposal. In Proceedings of the IEEE Real-Time Systems Symposium (RTSS), pages 13–26, 2023. doi:10.1109/RTSS59052.2023.00012.
  • [3] Alan Burns and Robert I. Davis. Mixed criticality systems: A review (13th edition, february 2022). Technical report, Department of Computer Science, University of York, February 2022.
  • [4] Vladimír Černý. Thermodynamical approach to the traveling salesman problem: An efficient simulation algorithm. Journal of Optimization Theory and Applications, 45(1):41–51, 1985. doi:10.1007/BF00940812.
  • [5] Stefan Draskovic, Rehan Ahmed, Pengcheng Huang, and Lothar Thiele. Schedulability of probabilistic mixed-criticality systems. Real-Time Systems, 57:397–442, 2021. doi:10.1007/S11241-021-09365-4.
  • [6] Ronald L. Graham. Bounds on multiprocessing timing anomalies. SIAM Journal on Applied Mathematics, 17(2):416–429, 1969.
  • [7] Fei Guan, Jinkyu Lee, Chun Jason Xue, Jen-Ming Wu, and Nan Guan. Mixed-criticality federated scheduling for relaxed-deadline dag tasks. In Proceedings of the 45th IEEE Real-Time Systems Symposium (RTSS). IEEE, 2024. doi:10.1109/RTSS62706.2024.00038.
  • [8] Zhishan Guo, Sudharsan Vaidhun, Luca Santinelli, Samsil Arefin, Jun Wang, and Kecheng Yang. Mixed-criticality scheduling upon permitted failure probability and dynamic priority. IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, 41(1):62–75, 2022. doi:10.1109/TCAD.2021.3053232.
  • [9] Qingqiang He, Nan Guan, Shuai Zhao, and Mingsong Lv. Multipath bound for DAG tasks. IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, 44(5):1676–1689, 2025. doi:10.1109/TCAD.2024.3507563.
  • [10] ISO 26262-1:2018 Road vehicles – Functional safety, 2018. URL: https://www.iso.org/standard/68385.html.
  • [11] Shinpei Kato, Eijiro Takeuchi, Yoshio Ishiguro, Yoshiki Ninomiya, Kazuya Takeda, and Toshiyuki Matsui. Autoware on board: Enabling autonomous vehicles with embedded systems. In Proceedings of the 9th ACM/IEEE International Conference on Cyber-Physical Systems, pages 287–296. ACM, 2018.
  • [12] Oliver R. Kelly, Hakan Aydin, and Baoxian Zhao. On partitioned scheduling of fixed-priority mixed-criticality task sets. Real-Time Systems, 49(6):736–777, 2013.
  • [13] Scott Kirkpatrick, C. Daniel Gelatt, and Mario P. Vecchi. Optimization by simulated annealing. Science, 220(4598):671–680, 1983. doi:10.1126/science.220.4598.671.
  • [14] Jian Li, Nan Guan, Mingsong Lv, Ge Peng, and Wang Yi. Semi-federated scheduling of mixed-criticality system for sporadic DAG tasks. In Proceedings of the 22nd IEEE International Symposium on Real-Time Distributed Computing (ISORC), pages 97–106. IEEE, 2019.
  • [15] Jing Li, Kunal Agrawal, Chenyang Lu, and Christopher D. Gill. Analysis of global EDF for parallel tasks. Real-Time Systems, 50(1):3–40, 2014.
  • [16] Risat Mahmud Pathan. Improving the schedulability and quality of service for federated scheduling of parallel mixed-criticality tasks on multiprocessors. In Proceedings of the 30th Euromicro Conference on Real-Time Systems (ECRTS), pages 12:1–12:22. Schloss Dagstuhl, 2018. doi:10.4230/LIPIcs.ECRTS.2018.12.
  • [17] Martin Stigge, Pontus Ekberg, Nan Guan, and Wang Yi. The digraph real-time task model. In Proceedings of the 17th IEEE Real-Time and Embedded Technology and Applications Symposium, pages 71–80. IEEE, 2011. doi:10.1109/RTAS.2011.15.
  • [18] Stephen Vestal. Preemptive scheduling of multi-criticality systems with varying degrees of execution time assurance. In Proceedings of the 28th IEEE International Real-Time Systems Symposium, pages 239–243. IEEE, 2007.
  • [19] Reinhard Wilhelm, Jakob Engblom, Andreas Ermedahl, Niklas Holsti, Stephan Thesing, David B. Whalley, Guillem Bernat, Christian Ferdinand, Reinhold Heckmann, Tulika Mitra, Frank Mueller, Isabelle Puaut, Peter P. Puschner, Jan Staschulat, and Per Stenström. The worst-case execution-time problem—overview of methods and survey of tools. ACM Trans. Embed. Comput. Syst., 7(3):1–53, 2008. doi:10.1145/1347375.1347389.
  • [20] Atsushi Yano and Takuya Azumi. RD-Gen: Random DAG generator considering multi-rate applications for reproducible scheduling evaluation. In Proceedings of the 26th IEEE International Symposium on Real-Time Distributed Computing (ISORC), pages 21–31, 2023. doi:10.1109/ISORC58943.2023.00015.