Implementation Guidelines

The JSON Processing profile measures how efficiently a framework handles a typical real-world API workload: loading data, computing derived fields, and serializing a JSON response.

How it works

1. At startup, the server reads /data/dataset.json — a file containing 50 items with mixed types (strings, numbers, booleans, arrays, nested objects)
2. On each GET /json/{count}?m={multiplier} request, the server:
   • Takes the first count items from the dataset (1–50)
   • Computes a total field (price × quantity × m) for each item — m is an integer path-query multiplier that varies per request template
   • Builds the response object
   • Serializes everything as JSON
3. Returns Content-Type: application/json

The benchmark round-robins across 7 fixed (count, m) pairs: (1, 3), (5, 7), (10, 2), (15, 5), (25, 4), (40, 8), (50, 6). Different multipliers per template mean every response body is unique — a framework that tries to cache GET /json/5 by path alone will return wrong totals for other requests.

What it measures

• Object allocation - 1–50 new objects built per request, varying across requests
• JSON serialization - converting native data structures to JSON text
• Mixed-type handling - strings, numbers, booleans, arrays, nested objects
• Route parameter parsing - extracting the count from the URL path
• Framework response overhead - buffering, headers, content-type handling

Dataset format

Each item in dataset.json:

{
  "id": 1,
  "name": "Alpha Widget",
  "category": "electronics",
  "price": 328,
  "quantity": 15,
  "active": true,
  "tags": ["fast", "new"],
  "rating": {
    "score": 48,
    "count": 127
  }
}

Expected response

For GET /json/5?m=3:

{
  "items": [
    {
      "id": 1,
      "name": "Alpha Widget",
      "category": "electronics",
      "price": 328,
      "quantity": 15,
      "active": true,
      "tags": ["fast", "new"],
      "rating": { "score": 48, "count": 127 },
      "total": 14760
    }
  ],
  "count": 5
}

The count field must match the number of items returned and the route parameter. The total field is computed as price * quantity * m (all integers — no rounding needed). The server must return the first count items from the dataset.

Parameters