#5192Requested

Cheap Static/Config data tables

Requested by @onx2
Energy Committed33,079TeVfrom 10 boosters

Right now it is reasonably expensive to load in physics, terrain, or nav data during a "tick" which is the hottest path. Ideally we have some first-class support for a cheap read-only table that can be initialized at startup. Right now there is the potential to use a const or static but with caveats so having the team support this pattern out of the box would be really valuable.

For example, I have navmesh grid data that is ~8mb. I need to load in ~200 bytes * 9 (for the chunks surround) per moving entity. So if I have 100 players and maybe 1000 monsters running around thats 1,1002009 potentially bytes read every ~100ms when I never need to edit this data.

I can simply add this data into a const and bundle it with the module but it doesn't feel like "the spacetimedb way" of doing things. If something is 100% read only I'd like a way to read that data for close to free instead of the charge at the same rate as hot data.

  1. website-features added the feature-request label Jun 3, 2026
  2. I can't edit the post but I guess I fat fingered the math and it didn't show up right, but you get the picture. Its expensive to load static data in a hot path

Boost this Request

Reopen this request?

The request will return to its prior live status.

Mark as Duplicate

Pick the request that Cheap Static/Config data tables 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.