Operator search is a core dimension of the Neural Architecture Search (NAS) search space, where an algorithm selects the type of layer operation—such as a standard convolution, depthwise convolution, pooling, or skip connection—to apply at each position in a network. This discrete optimization problem is fundamental to discovering novel, high-performance model topologies that would be infeasible to design manually. For hardware-aware NAS, the search evaluates operators not just for accuracy but also for their computational cost, memory footprint, and latency on target devices like microcontrollers.
Glossary
Operator Search

What is Operator Search?
Operator search is the automated process of selecting the optimal mathematical operation for each layer within a neural network's architecture.
The search space for operators is defined by a predefined set of candidate primitives. In differentiable NAS methods like DARTS, a continuous relaxation allows the search to optimize selection via gradient descent. In reinforcement learning or evolutionary strategies, the search algorithm samples discrete choices. The goal is to find an architecture where the chosen operator at each layer collectively maximizes the objective, which for TinyML deployment is a multi-objective trade-off between task accuracy and severe hardware constraints like kilobyte-scale memory and microjoule-level energy consumption.
Key Features of Operator Search
Operator search is the discrete selection mechanism within Neural Architecture Search (NAS) that determines the fundamental mathematical operation applied at each layer of a neural network, directly impacting computational cost and hardware efficiency.
Discrete Operation Selection
Operator search selects from a predefined set of candidate operations for each layer or node in the computational graph. This is a discrete optimization problem, as the algorithm must choose one operation (e.g., a 3x3 convolution) over another (e.g., a 5x5 depthwise convolution). Common operation sets include:
- Standard Convolutions (e.g., 3x3, 5x5)
- Depthwise Separable Convolutions (dramatically reduce FLOPs)
- Pooling Operations (Max, Average)
- Identity/Skip Connections (enable residual learning)
- Dilated Convolutions (increase receptive field)
- Grouped Convolutions The choice directly dictates the layer's parameter count, FLOPs, and memory access patterns.
Integration with Search Space
Operator search is one of three primary axes in a typical NAS search space, working in concert with:
- Cell/Topology Search: Defines how nodes (layers) are connected.
- Channel/Skip Search: Determines the width (# of channels) and the use of residual connections. The search space is the Cartesian product of these choices. For example, a search space might allow choosing between 8 operations at each of 5 nodes within a cell, leading to 8^5 (32,768) possible operator configurations for that cell alone, before considering connectivity.
Hardware-Centric Objective
In Hardware-Aware NAS, operator search is guided by a multi-objective reward function that balances accuracy with hardware metrics. The search algorithm evaluates operators not just for accuracy but for their impact on:
- Inference Latency: Measured in milliseconds, often via a hardware cost model or on-device profiling.
- Peak Memory Usage: Critical for microcontrollers with KB of RAM.
- Energy Consumption: Measured in microjoules per inference.
- Model Size (Parameters): Affects flash storage. Operators like depthwise convolutions are frequently selected in hardware-aware searches due to their favorable FLOP-to-accuracy ratio.
Search Strategy Implementation
The mechanism for selecting operators varies by NAS methodology:
- Reinforcement Learning (RL-NAS): A controller RNN samples a probability distribution over operations.
- Evolutionary Algorithms: Operations are encoded in a genome and mutated/crossed over.
- Differentiable Search (DARTS): The hardest problem. A continuous relaxation is applied: each edge is assigned a set of architecture parameters (alpha) for all candidate operations. A softmax over these alphas creates a weighted mixed operation. After search, a discretization step selects the operation with the highest alpha, pruning the others. This allows efficient gradient-based optimization of the operator choice.
Impact on Final Architecture
The operator search results in a heterogeneous architecture where different layers use optimally selected, often different, operations. This contrasts with hand-designed networks which typically use repetitive blocks (e.g., all 3x3 convs). For example, a NAS-discovered network might sequence:
- A standard 5x5 conv for early feature extraction.
- A depthwise conv for efficient mid-level processing.
- A dilated conv to capture context without downsampling.
- A skip connection to preserve gradient flow. This heterogeneity is key to achieving superior efficiency-accuracy Pareto frontiers.
TinyML-Specific Optimizations
For microcontroller deployment, operator search incorporates extreme constraints:
- Fixed-Point Friendly Ops: Preference for operations (like ReLU) that quantize well vs. those that don't (like Swish).
- Kernel Size Constraints: Avoiding large kernels (7x7) that cause inefficient memory access on MCUs.
- Operator Fusion Awareness: Selecting sequences of operations (Conv + BatchNorm + ReLU) that can be fused into a single, efficient kernel during compilation.
- Flash Memory Footprint: The choice of operation affects the stored model size; complex operators require more code space. Searches may use MCU-in-the-loop profiling to get true latency/energy measurements for candidate operators.
Common Operators in a Search Space
A comparison of fundamental neural network operations considered within a Hardware-Aware NAS search space, detailing their computational characteristics and suitability for microcontroller deployment.
| Operator | Primary Use | Computational Cost (MACs) | Parameter Count | MCU Suitability |
|---|---|---|---|---|
Standard Convolution (Conv) | Feature extraction, spatial filtering | High | High | |
Depthwise Separable Convolution (DSC) | Lightweight feature extraction | Low | Low | |
Pointwise Convolution (1x1 Conv) | Channel mixing, dimensionality change | Medium | Medium | |
Max / Average Pooling | Spatial downsampling, translation invariance | Very Low | Zero | |
Dilated Convolution | Increased receptive field without pooling | Medium-High | Medium | |
Grouped Convolution | Reduced computation via channel groups | Medium | Medium | |
Identity / Skip Connection | Gradient flow, residual learning | Zero | Zero | |
Zero Operation (Drop Path) | Search space regularization | Zero | Zero |
Frequently Asked Questions
Operator search is a fundamental component of Neural Architecture Search (NAS) where an algorithm selects the specific mathematical operation to apply at each layer of a neural network. This FAQ addresses its core mechanics, role in hardware-aware optimization, and practical implementation.
Operator search is the component of a Neural Architecture Search (NAS) algorithm that selects the type of computational layer or operation (e.g., a 3x3 convolution, a 5x5 depthwise convolution, max pooling, or an identity skip connection) to be applied at each position within a neural network's computational graph. It defines the functional building blocks of the discovered architecture.
In practice, the search space for operators is discrete and predefined. For a cell-based search space, the algorithm might choose from a set like {3x3 conv, 5x5 conv, 3x3 depthwise conv, 5x5 depthwise conv, 3x3 avg pool, 3x3 max pool, identity, zero}. The goal is to find the optimal sequence and combination of these operators that maximizes accuracy while satisfying constraints like model size or latency.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Operator search is a critical dimension within the broader NAS framework. These related concepts define the search space, strategy, and hardware-specific constraints that shape the final discovered architecture.
Search Space (NAS)
The search space defines the universe of all possible neural network architectures an algorithm can explore. It is parameterized by fundamental building blocks:
- Node operations (e.g., convolution, pooling, identity)
- Connectivity patterns between nodes (e.g., sequential, residual, dense)
- Hyperparameters per layer (e.g., filter count, kernel size)
Operator search directly manipulates one axis of this space. A well-designed search space balances expressiveness (to find good models) with tractability (to make search feasible). Common patterns include cell-based spaces (searching for a repeating block) and hierarchical spaces.
Search Strategy (NAS)
The search strategy is the core algorithm that navigates the search space to find high-performing architectures. It defines how the search is conducted. Major strategy families include:
- Reinforcement Learning (RL): A controller network is trained to generate architectures, rewarded for high accuracy.
- Evolutionary Algorithms: A population of architectures is evolved using selection, mutation, and crossover.
- Gradient-Based Methods (e.g., DARTS): The search space is relaxed to be continuous, allowing architecture parameters to be optimized via gradient descent.
- Random Search & Bayesian Optimization: Used as efficient baselines. The strategy is decoupled from the search space; operator search can be integrated into any of these approaches.
Hardware Cost Model
A hardware cost model is a predictive function that estimates the real-world efficiency metrics of a candidate neural network architecture on specific target hardware. It is the bridge between the abstract search space and physical deployment constraints.
Types of Cost Models:
- Look-up Tables (LUTs): Pre-measured latency/energy for each operator on the target hardware. The model sums costs for a given graph.
- Analytical Models: Use roofline models or hardware performance equations.
- Neural Network Predictors: Small MLPs trained to predict latency or power from an architecture encoding.
These models allow the search algorithm (e.g., during operator selection) to optimize directly for metrics like inference latency, peak memory usage, or energy consumption without needing to deploy every candidate.
Differentiable Architecture Search (DARTS)
Differentiable Architecture Search (DARTS) is a seminal gradient-based NAS strategy that heavily influences modern operator search. It formulates the search space as a continuous supernet where each candidate connection between nodes is weighted by a continuous architecture parameter (alpha).
How it relates to Operator Search:
- The set of possible operations (conv3x3, conv5x5, pool, etc.) on an edge is treated as a mixed operation, weighted by these alpha parameters.
- The search jointly optimizes the supernet weights (via standard gradient descent) and the architecture parameters (via gradient descent on a validation set).
- After search, a discrete architecture is derived by selecting the operation with the highest alpha value on each edge. This provides an efficient, gradient-based method for differentiable operator selection.
Once-For-All (OFA)
Once-For-All (OFA) is a one-shot NAS and training paradigm designed for efficiency across diverse hardware constraints. It trains a single, large supernet that supports many sub-networks via weight sharing.
Its connection to Operator Search:
- The OFA search space includes multiple dimensions: depth, width, kernel size, and—critically—operators.
- The supernet is trained with progressive shrinking to ensure the shared weights are good for all sub-networks.
- After training, a specialized search (e.g., using a hardware cost model) is performed to extract the optimal sub-network for a given latency or memory target. This makes operator search a post-training selection step from a fixed, pre-trained set of possibilities, eliminating the cost of searching from scratch for each new constraint.
Microcontroller NAS (MCU-NAS)
Microcontroller NAS (MCU-NAS) refers to hardware-aware neural architecture search methods specifically engineered for the extreme constraints of microcontroller units (MCUs). It represents the most stringent application of operator search.
Key Differentiators:
- Constraints: Targets kilobyte-scale SRAM/Flash and microjoule-level energy budgets.
- Cost Model Fidelity: Requires extremely accurate models for MCU-specific operations (e.g., depthwise convolution, fixed-point arithmetic).
- Search Space Design: Heavily pruned to exclude operators prohibitively expensive on MCUs (e.g., large dense layers, standard convolutions). Favors operators like depthwise-separable convolutions, pooling, and ReLU.
- Objective: Discovers models that are not just accurate, but are compilable and runnable within the tiny memory footprint and low clock speeds of devices like Arm Cortex-M series chips.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us