Workload Design & Concurrency

Here is my production traffic data from the last 30 days:
[Paste Datadog / Grafana / CloudWatch metrics or describe: peak RPS, average RPS, peak concurrent users]

Design a realistic workload model for performance testing:
- Concurrency model (open vs closed)
- VU ramp-up profile (step, linear, spike)
- Transaction mix (%) based on production ratios
- Think time and pacing recommendations
- Test duration for each test type
- Load profile diagram (ASCII or table)

Help me calculate the required virtual users using Little's Law.

Given:
- Target throughput (λ): [N requests/second]
- Average response time (W): [N milliseconds]
- Think time: [N seconds]

Show the full calculation, explain each variable, and tell me what VU count to configure in JMeter / k6.

My application has the following user actions based on analytics:
- [Action 1]: [% of traffic]
- [Action 2]: [% of traffic]
- [Action 3]: [% of traffic]

Design a transaction mix for performance testing that:
- Mirrors production proportionally
- Accounts for seasonal variation
- Handles dependencies between transactions
- Works with JMeter Thread Groups or k6 scenarios

Show the mix as a table and provide the JMeter / k6 configuration approach.

Design a ramp-up profile for the following test scenario:

Test type: [load / stress / spike / soak]
Target VUs: [N]
SLA: p95 < [N]ms, error rate < [N]%
Duration: [N minutes]
Application warm-up time: [N seconds]

Provide:
- Step-by-step ramp-up table (time → VUs)
- JMeter Thread Group configuration values (ramp-up, hold, ramp-down)
- k6 stages array equivalent
- Rationale for the chosen profile