Skip to main content
Challenge

Build a Spot Accelerator Preemption and Checkpoint Recovery Simulator

Simulate spot preemption events and KV-cache recovery costs across heterogeneous open-model workers. Plan migration schedules and evaluate resumption overhead using hosted Claude.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Simulate spot preemption events and KV-cache recovery costs across heterogeneous open-model workers. Plan migration schedules and evaluate resumption overhead using hosted Claude.

Distributed Training and Serving Architect

Model synthetic cloud accelerator spot termination notices with variable countdown windows.

Calculate uncommitted KV-cache flush times and checkpoint state transfer latencies across nodes.

Use hosted Claude API to synthesize a failover sequence that minimizes request dropped-token counts.

Produce an incident replay report detailing service degradation and cost recovery.

Chaos-engineering console with preemption trigger buttons and timeline reconstruction.

Simulated cloud termination event streams and distributed state snapshot metrics in test JSON. Starter examples below are synthetic. They are not downloaded records.

AWS Neuron documentation Models AWS EC2 spot lifecycle behavior and accelerated instance preemption intervals.

ray-serve, anthropic-claude, pydantic-ai. Provides deployment abstractions for distributed inference actors and replica state migration. Hosted Claude API for post-preemption recovery planning; strictly remote API.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Accurately simulates 120-second cloud spot preemption notice constraint.

Quantifies time required to serialize and migrate open-model serving context.

Formulates worker draining sequence that avoids hard connection drops for active users.

Outputs complete JSON recovery audit trail without invoking live cloud APIs.

```json [ { "input": { "preempted_node": "spot-worker-inf2-09", "notice_window_sec": 120, "active_requests": 8, "kv_cache_state_mb": 420, "interconnect_egress_mbps": 100, "backup_target_node": "on-demand-worker-inf2-01" }, "expected_output": { "transfer_duration_sec": 4.2, "migration_feasible": true, "action_sequence": [ "Mark spot-worker-inf2-09 as unschedulable in router.", "Flush 420MB active KV context to on-demand-worker-inf2-01 (4.2s estimated).", "Drain in-flight generation requests with remaining 115.8s buffer.", "Deregister spot worker instance prior to hardware termination." ], "dropped_request_count": 0 } }, { "input": { "preempted_node": "spot-worker-g5-02", "notice_window_sec": 15, "active_requests": 40, "kv_cache_state_mb": 2400, "interconnect_egress_mbps": 50, "backup_target_node": "on-demand-worker-g5-01" }, "expected_output": { "transfer_duration_sec": 48, "migration_feasible": false, "action_sequence": [ "Insufficient time for full context migration (48s required vs 15s window).", "Abort KV-cache serialization to preserve network egress.", "Reroute 40 active requests to fallback queue with prompt re-prefill.", "Issue emergency worker disconnect signal." ], "dropped_request_count": 40 } } ] ```

Simulates preemption logic without executing cloud VM termination commands. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Simulates preemption logic without executing cloud VM termination commands. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Accurately simulates 120-second cloud spot preemption notice constraint. Quantifies time required to serialize and migrate open-model serving context. Formulates worker draining sequence that avoids hard connection drops for active users. Outputs complete JSON recovery audit trail without invoking live cloud APIs.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Model synthetic cloud accelerator spot termination notices with variable countdown windows. Calculate uncommitted KV-cache flush times and checkpoint state transfer latencies across nodes. Use hosted Claude API to synthesize a failover sequence that minimizes request dropped-token counts. Produce an incident replay report detailing service degradation and cost recovery.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Accurately simulates 120-second cloud spot preemption notice constraint. Quantifies time required to serialize and migrate open-model serving context. Formulates worker draining sequence that avoids hard connection drops for active users. Outputs complete JSON recovery audit trail without invoking live cloud APIs.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Chaos-engineering console with preemption trigger buttons and timeline reconstruction.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Simulates preemption logic without executing cloud VM termination commands.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Model synthetic cloud accelerator spot termination notices with variable countdown windows.

  • Calculate uncommitted KV-cache flush times and checkpoint state transfer latencies across nodes.

  • Use hosted Claude API to synthesize a failover sequence that minimizes request dropped-token counts.

  • Produce an incident replay report detailing service degradation and cost recovery.

Resources and assets

Reference links and supporting material

Dataset notes

Simulated cloud termination event streams and distributed state snapshot metrics in test JSON. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Ray Serve

Action Space in the agent workflow.

Evaluated output

No output checks are configured.

Evaluation checks
  • Model synthetic cloud accelerator spot termination notices with variable countdown windows. Calculate uncom...
  • Accurately simulates 120-second cloud spot preemption notice constraint. Quantifies time required to serial...
  • Chaos-engineering console with preemption trigger buttons and timeline reconstruction.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Ray Serve · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Spot Accelerator Preemption and Checkpoint Recovery Simulator