Sweeper Configuration
Core fields and optional adapter-owned search spaces
<!—
Generated from aisimulate/docs/sweeper/configuration.md by docs/fern/scripts/sync_aisimulate_docs.py.
Edit the canonical source instead of this Fern copy.
—>
SmartSearchConfig.search_space contains backend and deployment fields. Optional feature-specific
search spaces are mappings under SmartSearchConfig.adapters.
Top-Level Shape
The adapter value is a search space, not one concrete runtime configuration. Its provider validates the whole mapping, contributes optimizer dimensions, and later materializes one concrete adapter configuration for each candidate.
Backend Fields
Each engine role also has lists for max_num_batched_tokens and max_num_seqs, plus pinned block
size, GPU-memory-utilization, and prefix-caching fields. A one-item list pins a searched field.
Pinned Parallel Configurations
Pinning parallel_configs requires exactly one deployment mode. An aggregated entry is one shape:
A disaggregated entry contains prefill and decode shapes. Every pinned shape must be legal,
KV-feasible, and supported by at least one selected backend.
Provider Selection
Adapter names are provider entry-point names. A provider can be installed through the
aisimulate.sweep_config_providers entry-point group or injected into the Sweeper constructor:
Sweeper loads only names present under adapters. See Sweep Configuration
Providers for the complete ABI.
Sampler Algorithm Override
The experimental AISIMULATE_SWEEPER_VIZIER_ALGO environment variable overrides the Vizier
algorithm. For example, set it to RANDOM_SEARCH to bypass the default GP-bandit designer.
SPICA_VIZIER_ALGO remains a deprecated fallback during migration; when both are set, the
AI Simulate variable takes precedence.
Removed KVBM Fields
Sweeper rejects the old KVBM block-count, transfer-bandwidth, offload-batch-size, and cache-hit fields. Native G2 replaces KVBM, so these fields have no adapter migration.