Performance Targets
Pipeline Optimization
1. Use PLAN_ONLY for Preview Calls
If your agent has a planning loop that evaluates actions before committing, use PLAN_ONLY mode to skip evidence emission and post-hooks:2. Minimize Registered Modules
Each module adds parallel evaluation time. Only register modules you need:3. Use regex_only Mode When ML Isn’t Needed
TealClassifier’sensemble_union mode loads an ONNX model. If you only need pattern matching, use regex_only:
4. Tune Drift Baseline Window
Larger baseline windows mean more data to compare. For high-throughput agents, reduce the window:Memory Optimization
Reduce Classifier Memory
If you don’t need ML classification, don’t load the ONNX model:Limit Drift Tracking
For systems with many agents, limit how many baselines are tracked:Post-Hook Optimization
Post-evaluation hooks run after the decision is computed. Make them non-blocking:- Use
trigger: 'on_deny'instead of'always'to reduce hook invocations - Set
dedup_window_msto suppress repeated violations - Set
rate_limitto prevent webhook flooding - Hooks are async — they don’t block the decision response
Sidecar Optimization
For Docker sidecar deployments:Benchmarking
Run the built-in benchmark suite to measure your specific configuration:When Performance Matters Less
Not every deployment needs sub-10ms governance. Consider your context:
For most AI agent workloads, TealTiger’s default < 25ms p99 is well within acceptable bounds — LLM calls themselves take 500ms-5s.
Related Documentation
Limits & Defaults
All default values and performance targets
Configuration
Module and engine configuration options

