LogoLogo
  • Overview
    • Intro
    • Fair Math Actor
      • Fair Math Controller
      • Fair Math VM
      • Setup an Actor
    • Hello (CIFAR) world!
  • FHE Computer
    • Overview
    • Architectural Layers
      • Application Layer
      • Orchestration Layer
      • Verification Layer
      • Execution Layer
      • Data Layer
    • ISA
      • fhe
      • arith
      • tensor
      • polycircuit
    • Operating System
      • Computer State
      • Application
        • Running Applications
        • External Functions
        • Interactive APPS
      • Execution Graph and Tasks
        • Atomic and Composite Instructions
        • Instruction Unrolling
        • Task Dependencies
        • Execution Graph
      • Process
        • Process lifecycle
        • Resource Allocation and Isolation
      • Order Book
        • Matching Mechanism
        • Task Complexity
        • Instruction Complexity
        • Task re-Delegation
      • Context
        • Context Structure
      • FHE Component Repository
    • Fair Math Actors
      • Task State Monitoring
      • Execution Pairs
      • Rewards and Penalties
    • Ethereum Endpoint
    • CIFAR10 App
  • Whitepapers
    • FHE Computer
    • FHERMA
  • FHERMA
  • Resources
    • Computer CLI
    • FHERMA
    • POLYCIRCUIT (CPP)
    • OpenFHE-rs
    • Talks and Podcasts
  • Social
    • Twitter
    • Linkedin
    • Website
    • Github
Powered by GitBook
LogoLogo
On this page
  1. FHE Computer
  2. Operating System
  3. Execution Graph and Tasks

Execution Graph

PreviousTask DependenciesNextProcess

Last updated 5 months ago

The breakdown of a function into tasks is represented as a directed acyclic graph (DAG), called the execution graph. The graph consists of:

  • Nodes (Tasks): Each task in the function is a node in the graph.

  • Edges (Dependencies): Directed edges between tasks represent dependencies, meaning one task must be completed before another can start.

Key Features of the Execution Graph

  1. Dynamic Refinement: The orchestration layer can break tasks into smaller subtasks if needed, allowing for more flexible and efficient scheduling.

  2. Instruction Expansion: Composite instructions within tasks can be expanded into their atomic components, ensuring they can be executed by available resources.

This adaptability allows the system to optimize task execution based on available resources and workload while maintaining proper dependency order.

Page cover image
Execution graph example