clockworklabs / clockworklabs/SpacetimeDB

Execution metrics for views

Open
#3,767 0 comments 0 reactions 1 assignee View on GitHub

@Shubham8287 is already working on this.

Since Dec 11, 2025.

Dominant language
Rust
Stars
25.2k
Forks
1.1k
Avg merge
2d 7h
Merged PRs (30d)
46

Description

Currently we can split the execution of a reducer into at least three distinct phases:

  1. The reducer call
  2. View update
  3. Subscription update

We have reducer and subscription level metrics, but we don't have any view-level metrics. We'd like to know things like:

  • Call rates for views
  • Execution times for views
  • How much do views contribute to total transaction time
  • Read set sizes for views
  • Subscribers

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.