Request Details

it would be nice to have a dataflow schematic of how spacetimedb works.
where in the function chains gets the data copied into and from wasm:

  • ctx.db.table().column().find()
  • ctx.db.table().index().filter()
  • ctx.db.table().insert()
  • ctx.db.table().column().delete()
  • ctx.db.table().column().update()
  • ctx.db.table().iter()
  • when and where views run.
  • how the subscription response get's calculated
  • where and how the clog get's written
  • how the error rollback works. (do attempted row writes get counted to the energy cost?)
  • what runs in it's own thread? what uses more than one core? what shares a core?

and so on
it's basically about how to optimize and write stdb by understanding what is happening with the data inside and outside of wasm.

  1. website-features added the feature-request label Jun 19, 2026

Reopen this request?

The request will return to its prior live status.

Mark as Duplicate

Pick the request that Docs: Dataflow schematic of Stdb is a duplicate of. Energy rolls up into that request and GitHub closes the linked issue as a duplicate with a timeline reference to the canonical.

Unmark Duplicate

Restore as an independent request. The linked GitHub issue will be reopened and its duplicate-of relationship cleared. The original timeline entries stay as history; the note below is posted as a follow-up comment.