LAMINAR
New Migration
operations

Orders Table → DynamoDB

Running

orders-mysql-primaryddb-orders-global · MySQL 8 → DynamoDB · 38 datasets · running for 44m

Migration progress
18.6%118.9 GB of 640.0 GB
ETA 24m at current rate
Consistency: Change-stream tail (eventual cutover)
Current throughput
361 MB/s
Est. safe capacity
410 MB/s
Controller confidence
91%
model converged
Concurrency
16 / 64
workers × shards
p99 latency
12.1 ms
baseline 12.1 ms
Throttling
None
0 events this run
Adaptive Control Loop

One loop, running continuously against every target.

Stage · Observe
  1. 01
    Observe
  2. 02
    Estimate
  3. 03
    Probe
  4. 04
    Learn
  5. 05
    Adapt
  6. 06
    Checkpoint
  7. 07
    Recover
Rate control

Throughput, capacity ceiling and latency

Amber markers are rate changes issued by the controller. Utilisation of the current estimate is 88.0%.

Actual throughputEstimated safe capacityTarget ratep99 latencyRate change
Controller Decisions

Every rate change, with the observation that caused it.

  • 20:21:01INCREASE+8%

    Increased throughput by 8% — target latency remained stable across two probe windows.

  • 20:21:56HOLD

    Held throughput — feedback indicated rising latency at the current rate.

  • 20:23:00REDUCE-15%

    Reduced throughput by 15% after throttling was detected on the destination.

  • 20:23:21CHECKPOINT

    Checkpoint written — partition-8421 verified.

  • 20:23:40PROBE+3%

    Probe window opened — nudging 3% above estimate to keep the capacity model honest.

Recovery
Last verified checkpoint
partition-8421
116.5 GB verified
20:21:49 UTC · 6 minutes ago

On interruption Laminar resumes from the last verified checkpoint. Worst case is minutes of replay, not a restart.

  • partition-8421116.5 GB20:21:49
Audit timeline
  • 19:42:49Operation started

    orders-mysql-primary → ddb-orders-global, adaptive mode: Conservative (capacity-units aware)

  • 19:43:29Capacity model initialised

    Initial estimate 410 MB/s from 40s observation window