Load Test 2 DWD Idle

High-throughput inserter using a service account with Domain-Wide Delegation — scales linearly with pool size.

DWD Configuration Status

Key file found — 3 user(s) configured

Setup steps (one-time):
  1. GCP Console → IAM → Service Accounts → Create → download JSON key → save as tokens/lt-service-account.json
  2. GCP Console → note the service account's Client ID (numeric)
  3. Google Workspace Admin → Security → API controls → Domain-wide delegation → Add client ID → scope: https://www.googleapis.com/auth/calendar
  4. Add to .env:
    LT_SERVICE_ACCOUNT_KEY_PATH=./tokens/lt-service-account.json
    LT_IMPERSONATION_USERS=user1@domain.com,user2@domain.com,...
    LT_DWD_CONCURRENCY_PER_USER=10
  5. Restart the server

Calendar Registry

2000 rooms in registry (building: LoadTest)

Configuration

Must not exceed rooms in registry
Window starts at now() — nothing is placed in the past
Spread evenly across the window — no overlaps up to 3 per room per hour, overlapping above that
Parallel batches per impersonated user. Total = users × this value.

Verification Settings — used by the auto-verify run that starts alongside every insert


Changes (churn) — moves, renames and deletes applied once an event has been shown by the external system. All 0 = insert only.

New time in the same room, free slot only
Several changes to the same event at a fixed gap
Alternating move / rename
Each rapid event uses one gap, spread evenly
Showing an old state after this long = stale
Shares the DWD users' quota with the insert
Deleted a fixed delay after creation, without waiting for the external system
Quick delete, then a NEW meeting in the same slot
Create → delete delay, spread evenly
Create → shown → delete → room left quiet; the next create is the poke. 0 = off
Nothing else changes in the room during this time
Stream of single changes per verified room. 0 = off
One phase per value, in the rooms without verifier credentials
Long enough for the server's 60-minute refetch

Insert Events

Events are tagged loadtest2: true and prefixed [LT2] so they can be cleaned up independently from Load Test 1.


Cleanup Events

Uses the admin account (same as Load Test 1 cleanup). Filter by run ID to clean up one run only.

Progress

No job running