adobe-load-scale

Implement Adobe load testing, auto-scaling, and capacity planning strategies. Use when running performance tests, configuring horizontal scaling, or planning capacity for Adobe integrations. Trigger with phrases like "adobe load test", "adobe scale", "adobe performance test", "adobe capacity", "adobe k6", "adobe benchmark".

claude-code
5 Tools
adobe-pack Plugin
saas packs Category

Allowed Tools

ReadWriteEditBash(k6:*)Bash(kubectl:*)

Provided by Plugin

adobe-pack

Claude Code skill pack for Adobe (30 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the adobe-pack plugin:

/plugin install adobe-pack@claude-code-plugins-plus

Click to copy

Instructions

Adobe Load & Scale

Overview

Load testing, scaling strategies, and capacity planning for Adobe integrations.

Prerequisites

  • k6 load testing tool installed
  • Kubernetes cluster with HPA configured
  • Prometheus for metrics collection
  • Test environment API keys

Load Testing with k6

Basic Load Test


// adobe-load-test.js
import http from 'k6/http';
import { check, sleep } from 'k6';

export const options = {
  stages: [
    { duration: '2m', target: 10 },   // Ramp up
    { duration: '5m', target: 10 },   // Steady state
    { duration: '2m', target: 50 },   // Ramp to peak
    { duration: '5m', target: 50 },   // Stress test
    { duration: '2m', target: 0 },    // Ramp down
  ],
  thresholds: {
    http_req_duration: ['p(95)<500'],
    http_req_failed: ['rate<0.01'],
  },
};

export default function () {
  const response = http.post(
    'https://api.adobe.com/v1/resource',
    JSON.stringify({ test: true }),
    {
      headers: {
        'Content-Type': 'application/json',
        'Authorization': `Bearer ${__ENV.ADOBE_API_KEY}`,
      },
    }
  );

  check(response, {
    'status is 200': (r) => r.status === 200,
    'latency < 500ms': (r) => r.timings.duration < 500,
  });

  sleep(1);
}

Run Load Test


# Install k6
brew install k6  # macOS
# or: sudo apt install k6  # Linux

# Run test
k6 run --env ADOBE_API_KEY=${ADOBE_API_KEY} adobe-load-test.js

# Run with output to InfluxDB
k6 run --out influxdb=http://localhost:8086/k6 adobe-load-test.js

Scaling Patterns

Horizontal Scaling


# kubernetes HPA
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: adobe-integration-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: adobe-integration
  minReplicas: 2
  maxReplicas: 20
  metrics:
    - type: Resource
      resource:
        name: cpu
        target:
          type: Utilization
          averageUtilization: 70
    - type: Pods
      pods:
        metric:
          name: adobe_queue_depth
        target:
          type: AverageValue
          averageValue: 100

Connection Pooling


import { Pool } from 'generic-pool';

const adobePool = Pool.create({
  create: async () => {
    return new AdobeClient({
      apiKey: process.env.ADOBE_API_KEY!,
    });
  },
  destroy: async (client) => {
    await client.close();
  },
  max: 20,
  min: 5,
  idleTimeoutMillis: 30000,
});

async function withAdobeClient<T>(
  fn: (client: AdobeClient) => Promise<T>
): Promise<T> {
  const client = await adobePool.acquire();
  try {
    return await fn(client);
  } finally {
    adobePool.release(client);
  }
}

Capacity Planning

Metrics to Monitor

Metric Warning Critical
CPU Utilization > 70% > 85%
Memory Usage > 75% > 90%
Request Queue Depth > 100 > 500
Error Rate > 1% > 5%
P95 Latency > 1000ms > 3000ms

Capacity Calculation


interface CapacityEstimate {
  currentRPS: number;
  maxRPS: number;
  headroom: number;
  scaleRecommendation: string;
}

function estimateAdobeCapacity(
  metrics: SystemMetrics
): CapacityEstimate {
  const currentRPS = metrics.requestsPerSecond;
  const avgLatency = metrics.p50Latency;
  const cpuUtilization = metrics.cpuPercent;

  // Estimate max RPS based on current performance
  const maxRPS = currentRPS / (cpuUtilization / 100) * 0.7; // 70% target
  const headroom = ((maxRPS - currentRPS) / currentRPS) * 100;

  return {
    currentRPS,
    maxRPS: Math.floor(maxRPS),
    headroom: Math.round(headroom),
    scaleRecommendation: headroom < 30
      ? 'Scale up soon'
      : headroom < 50
      ? 'Monitor closely'
      : 'Adequate capacity',
  };
}

Benchmark Results Template


## Adobe Performance Benchmark
**Date:** YYYY-MM-DD
**Environment:** [staging/production]
**SDK Version:** X.Y.Z

### Test Configuration
- Duration: 10 minutes
- Ramp: 10 → 100 → 10 VUs
- Target endpoint: /v1/resource

### Results
| Metric | Value |
|--------|-------|
| Total Requests | 50,000 |
| Success Rate | 99.9% |
| P50 Latency | 120ms |
| P95 Latency | 350ms |
| P99 Latency | 800ms |
| Max RPS Achieved | 150 |

### Observations
- [Key finding 1]
- [Key finding 2]

### Recommendations
- [Scaling recommendation]

Instructions

Step 1: Create Load Test Script

Write k6 test script with appropriate thresholds.

Step 2: Configure Auto-Scaling

Set up HPA with CPU and custom metrics.

Step 3: Run Load Test

Execute test and collect metrics.

Step 4: Analyze and Document

Record results in benchmark template.

Output

  • Load test script created
  • HPA configured
  • Benchmark results documented
  • Capacity recommendations defined

Error Handling

Issue Cause Solution
k6 timeout Rate limited Reduce RPS
HPA not scaling Wrong metrics Verify metric name
Connection refused Pool exhausted Increase pool size
Inconsistent results Warm-up needed Add ramp-up phase

Examples

Quick k6 Test


k6 run --vus 10 --duration 30s adobe-load-test.js

Check Current Capacity


const metrics = await getSystemMetrics();
const capacity = estimateAdobeCapacity(metrics);
console.log('Headroom:', capacity.headroom + '%');
console.log('Recommendation:', capacity.scaleRecommendation);

Scale HPA Manually


kubectl scale deployment adobe-integration --replicas=5
kubectl get hpa adobe-integration-hpa

Resources

Next Steps

For reliability patterns, see adobe-reliability-patterns.

Ready to use adobe-pack?