Summary

• Centralize REST and MCP endpoint mixes into shared JMeter fragments and render them into runnable plans before each JMeter target.
• Preserve weighted vs random mixes via REST_MIX_MODE / MCP_MIX_MODE so baseline vs load/stress/spike/soak keep distinct distributions.
• Remove two conditional REST endpoints that fail on localhost defaults.

Implementation

• Shared fragments: tests/jmeter/fragments/rest_mix.jmx, tests/jmeter/fragments/mcp_mix.jmx.
• Renderer: tests/jmeter/render_fragments.py generates .jmeter/rendered/*.jmx and Make targets run the rendered plans.
• Plan templates now include shared mixes and set mix-mode defaults; tests/jmeter/README.md documents the render step.

APIs Hit (high level)

• Health/metrics: /health, /ready, /version, /metrics, /metrics/prometheus, /api/metrics/*
• Core registries (read): /tools, /servers, /gateways, /resources, /prompts, /tags, /roots, /resources/templates/list
• RBAC read: /rbac/my/roles, /rbac/my/permissions, /rbac/permissions/available, /rbac/roles
• Model catalogs: /v1/models, /llm/gateway/models, /llmchat/gateway/models
• Other reads: /a2a, /tokens, /tokens/admin/all, /reverse-proxy/sessions, /api/logs/*, /import/status, /export
• MCP JSON-RPC (via /servers/{id}/mcp): initialize, tools/list, tools/call, resources/list, resources/read, prompts/list, ping

Missing / Not Covered (examples)

• Write/mutate operations (POST/PUT/PATCH/DELETE) across tools/resources/prompts/servers/gateways/tokens/RBAC, etc.
• Most Admin UI traffic and streaming endpoints (covered by their own dedicated JMeter plans, not part of the shared mixes).
• Conditional endpoints removed for now: /.well-known/oauth-protected-resource (404) and /auth/email/me (422) in the default localhost config.

Expands on [TESTING][PERFORMANCE]: JMeter Performance Load Testing Baseline #2541