Dispatcher Performance Tuning (AMS)
Improve cache efficiency, latency, and throughput for AMS deployments that use the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration.
Variant Scope
- This skill is AMS-only.
- Scope is fixed by this skill directory; do not ask the user to choose deployment variant.
MCP Tool Contract
Use only these Dispatcher MCP tools:
validatelintsdktrace_requestinspect_cachemonitor_metricstail_logs
Workflow
- Capture baseline metrics and cache evidence.
- Apply AMS 6.5 guardrails (tier boundaries, variable-driven config, flush ACL safety) to candidate optimizations.
- Prioritize low-risk/high-impact changes.
- Apply minimal edits.
- Verify with
validate,lint, andsdk. - Compare before/after runtime evidence.
Verification Scope Selection
Use shared references to select optimization evidence depth:
Output Contract
Always return:
- baseline metrics snapshot
- prioritized optimization list with impact/risk
- changed files and intent
- executed checks + before/after evidence
- selected test IDs and outcomes
- rollback plan and open risks
Guardrails
- Do not claim improvement without measurable comparison.
- Keep high-risk tuning opt-in unless user explicitly requests it.
- Keep AMS assumptions explicit for each recommendation batch.
References
- optimization-patterns.md
- performance-scenario-playbooks.md – scenario-driven tuning flows adapted from broader MCP prompt surfaces
- load-testing-guidance.md
- performance-monitoring-setup.md
- quick-start-execution-path.md – fast entry path for optimization requests
- repo-layout-workflows.md – map performance findings to cache, farm, vhost, rewrite, and variable file families
- playbook-command-linkage.md – exact MCP command chains for tuning playbooks
- ams-6-5-guardrails.md
- mode-specific-verification-matrix.md
- test-case-catalog.md
- change-risk-and-rollback-template.md
- public-docs-index.md
- public-doc-citation-rules.md
- core-7-tools-reference.md