#2363Requested

SpacetimeDB supports for hashmap indexing

Requested on GitHub by vovacooper
Energy Committed0TeV

would love to see an option to index a table not only in btree but also as hashmap.
(like hash index on postgres https://www.postgresql.org/docs/current/hash-index.html)

please please please add this

  1. Hey @vovacooper! Can you help us understand why this is so important for you?

  2. bfops added the feature-request label Apr 2, 2025
  3. hello @bfops !
    i personally would love this feature to be able to find data (like vector3) in O(1) time for my voxel world.

  4. Hey @Frisk197! I can say that BitCraft is currently using btree indexes for their world, and it's working well for them (on top of chunking, similar to what Minecraft does).

    Are you seeing performance issues in your project?

  5. @bfops
    yes i do have a performance issue, but i'm not sure if it's some limitation of spacetimedb or my dogshit code X)

    I'm trying to send a list of 10 positions to the server every 100ms.
    it's supposed to do a fast voxel traversal from the origin of the scan to all the points to remove any points in between and then add the point to the database but sometimes it can take 4 seconds for some reason.

    here's a test repository with some parts of my project to reproduce the problem : https://github.com/Frisk197/SaKADo_TEST
    i'm making an xr app but with this setup you can just start the app in unity

  6. i was asked on the discord to make a new issue : https://github.com/clockworklabs/SpacetimeDB/issues/3394

  7. Centril closed this as duplicate Jan 8, 2026

Boost this Request

Reopen this request?

The request will return to its prior live status.

Mark as Duplicate

Pick the request that SpacetimeDB supports for hashmap indexing 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.