Skip to content

perf(gateway): omit world catalogues from dedicated Realm-core - #715

Merged
Mathih13 merged 3 commits into
mainfrom
perf/realm-capacity
Oct 16, 2026
Merged

Mathih13 merged 3 commits into
mainfrom
perf/realm-capacity

Conversation

@Mathih13

@Mathih13 Mathih13 commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

A dedicated Realm-core Coordinator subscribes world catalogues that its Mail, auction and control work does not use. Those subscriptions add cache rows to the Gateway.

Omit 30 world catalogue queries only when Realm-core is separate from every configured World Shard. Retain item catalogues, faction relationships, control rows and all Relay tables. Save the subscription role so reconnect restores it. Mixed-role and idle World Shards keep their full subscriptions.

Part 6 of 6. Follows #714. Merged in stack order.

Verification

CI now tests dedicated and mixed Realm-core subscriptions with private Module fixtures, including retained Mail and auction reads and reconnect behavior.

Independent adversarial review and the CI fixture follow-up are complete. No actionable finding remains. The stack at 3dca984 passed offline binding generation, formatting, workspace Clippy with all targets and features, and the Gateway unit and integration test targets. The Gateway binary passed 2,148 tests. Local builds used one job; no local SpacetimeDB instance or load test ran.

All nine checks passed at abef2faf: Module durable tests and Gateway bindings, Runtime Scripts, Rust.

Comment review passed for the final changed source, tests, scripts and configuration. Retained protocol and ordering contracts match the code.

The first durable run exposed an in-memory fixture used for named Shards. The follow-up uses persistent storage, seeds the retained faction row explicitly, and expects no alternate route for the default World Shard. The final fixture compiled with --no-run; formatting and its independent source and comment reviews passed. Both dedicated and mixed Realm-core scenarios then passed in durable CI, including their checks after reconnect.

Verification limits

No cache-memory or capacity measurements were run. No capacity gain is claimed.

Risk

The omitted catalogues must stay unused by dedicated Realm-core operations. The change keeps all dynamic, control and Relay queries. It does not unsubscribe idle World Shards.

Models: GPT-6 Astra and GPT-6.1 Sol. Harness: Codex in T3 Code.

@Mathih13
Mathih13 force-pushed the perf/shared-relay-packets branch from 5ed6fd8 to ea8a1d9 Compare October 16, 2026 06:21
@Mathih13
Mathih13 force-pushed the perf/realm-capacity branch from 30195d2 to 3dca984 Compare October 16, 2026 06:21
@Mathih13
Mathih13 changed the base branch from perf/shared-relay-packets to main October 16, 2026 06:58
@Mathih13
Mathih13 merged commit f4eed65 into main Oct 16, 2026
9 checks passed
@Mathih13

Copy link
Copy Markdown
Contributor Author

Merged after adversarial review and repairs. Added dedicated and mixed Realm-core fixtures that check retained Mail and auction reads, catalogue subscriptions, and reconnect behavior. The first CI run found a fixture storage error. The fixture repair uses persistent storage, seeds the faction row, and fixes the expected default Shard route. Both scenarios now pass in durable CI.

All nine checks passed at abef2faf: Module durable tests and Gateway bindings, Runtime Scripts, Rust.

Comment review passed. Dedicated Realm-core omits the unused world catalogue subscriptions; mixed Realm-core retains them. No cache-memory or capacity gain is claimed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant