ExecutionStrategy

enum class MayaFlux::Kriya::ExecutionStrategy : uint8_t

strong

Defines how operations in a pipeline are coordinated and executed.

Enumerator
PHASED	PHASED: Traditional phased execution (default) All CAPTURE operations complete first (capture phase) Then all processing operations execute (process phase) Best for: accumulation, windowed analysis, batch processing Predictable data availability, clear phase boundaries
STREAMING	STREAMING: Immediate flow-through execution. Each capture iteration flows immediately through dependent operations Minimal latency, data processed as it arrives Best for: real-time effects, low-latency processing, modify_buffer chains Natural for operations that modify state continuously
PARALLEL	PARALLEL: Concurrent capture with synchronization. Multiple capture operations can run concurrently Explicit synchronization points coordinate data flow Best for: multi-source capture, independent data streams
REACTIVE	REACTIVE: Data-driven reactive execution. Operations execute when input data becomes available Dynamic dependency resolution Best for: event-driven workflows, complex dependencies Non-deterministic execution order

Definition at line 41 of file BufferOperation.hpp.

                                 : uint8_t {
        /**
         * PHASED: Traditional phased execution (default)
         * - All CAPTURE operations complete first (capture phase)
         * - Then all processing operations execute (process phase)
         * - Best for: accumulation, windowed analysis, batch processing
         * - Predictable data availability, clear phase boundaries
         */
        PHASED,
 
        /**
         * STREAMING: Immediate flow-through execution
         * - Each capture iteration flows immediately through dependent operations
         * - Minimal latency, data processed as it arrives
         * - Best for: real-time effects, low-latency processing, modify_buffer chains
         * - Natural for operations that modify state continuously
         */
        STREAMING,
 
        /**
         * PARALLEL: Concurrent capture with synchronization
         * - Multiple capture operations can run concurrently
         * - Explicit synchronization points coordinate data flow
         * - Best for: multi-source capture, independent data streams
         */
        PARALLEL,
 
        /**
         * REACTIVE: Data-driven reactive execution
         * - Operations execute when input data becomes available
         * - Dynamic dependency resolution
         * - Best for: event-driven workflows, complex dependencies
         * - Non-deterministic execution order
         */
        REACTIVE
    };