tursodatabase/turso

Per-query level cost statistics

Open

#3,136 opened on Sep 15, 2025

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Rust (1,001 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (19,103 stars)
PR merge metrics
 (PR metrics pending)

Description

When you're debugging a SQL query, it's extremely useful to have per-query level cost statistics, such as:

  • Duration
  • Rows processed
  • I/O throughput (MB/s)
  • Indexes used

The idea is that people can see the actual cost of a query as they execute it.

Contributor guide

Research direction
Investigate the query execution pipeline in Turso and identify where to hook in to collect cost metrics like duration, rows processed, I/O throughput, and indexes used.
Tech stack
rustsql
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75