← All workshopsRead Why Is One Storage Key Doing All the Work?

NoSQL

Find the maintenance key that concentrates traffic

BOTIE

Build Group traffic by the chosen key from the request trace and key-field list. Inspect the accumulated work before attaching the capacity comparison.
Ready to test
0 passed · 0 failed · 2 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.

Try your own inputs

Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Build Group traffic by the chosen key from the request trace and key-field list. Inspect the accumulated work before attaching the capacity comparison.

Requests arrive with tenant, asset and measured work.

Inspect the component calculation
Group traffic by the chosen key(
  Request measurements: Request trace
  Key field names: Chosen key fields
)
Examples and results
Request trace
[
  {
    "tenant": "north",
    "asset": "P7",
    "load": 6
  },
  {
    "tenant": "north",
    "asset": "P8",
    "load": 4
  }
]
Chosen key fields
  1. 0tenant
Required result
[
  {
    "key": [
      "north"
    ],
    "load": 10
  }
]
Request trace
[
  {
    "tenant": "north",
    "asset": "P7",
    "load": 6
  },
  {
    "tenant": "north",
    "asset": "P8",
    "load": 4
  },
  {
    "tenant": "north",
    "asset": "P7",
    "load": 5
  }
]
Chosen key fields
  1. 0tenant
  2. 1asset
Required result
[
  {
    "key": [
      "north",
      "P7"
    ],
    "load": 11
  },
  {
    "key": [
      "north",
      "P8"
    ],
    "load": 4
  }
]
Try a fresh construction

This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.

Stuck? Inspect a worked construction

The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.

Assumptions and test precision

Logical groups and invented work units do not simulate physical partitions or predict vendor throughput. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.

Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.

The same asset label appears in two tenants

This check uses the pieces from “Measure work grouped by a logical address”.

BOTIE

West’s P2 has request groups of four and three work units. East’s P2 has eight. The fields are tenant then asset, and capacity is seven. Predict the complete grouped-load result, including the boundary case.
Request trace
[
  {
    "tenant": "west",
    "asset": "P2",
    "load": 4
  },
  {
    "tenant": "east",
    "asset": "P2",
    "load": 8
  },
  {
    "tenant": "west",
    "asset": "P2",
    "load": 3
  }
]
Chosen key fields
  1. 0tenant
  2. 1asset
Teaching capacity
7

Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.

Build a construction in the workspace above first. This case will test those pieces.

What read work would a new day bucket or write shard introduce for a query over the whole history?

A partitioning change trades concentration against fan-out, ordering and migration work.

Logical groups and invented work units do not simulate physical partitions or predict vendor throughput.

Work through the Python challenges →
Continue the courseKeep One Asset’s History Together Without Growing Forever →
← How Much Urgent Work Was Hidden Inside the Pump Documents?