1
89%
main: 92%

Ran 10 Feb 2026 02:58PM UTC

Files 116

Run time 4s

Badge

Embed ▾

Committed 10 Feb 2026 02:51PM UTC coverage: 83.845% (+0.09%) from 83.751%

Job # 21869758251.1

Build Type

Pull #311

github

Committed by

cendhu

Commit Message

[vc] split tables into predefined number of tablets

When a new table is created, YugabyteDB starts with a single
tablet that handles ALL initial writes. Auto-splitting only kicks in after
the tablet reaches a size threshold (~1 GB by default), meaning the first
N transactions all funnel through one tablet on one tserver — creating a
severe bottleneck during the critical warm-up phase.

By pre-splitting tables at CREATE TABLE time (e.g., SPLIT INTO 3 TABLETS
for a 3-node cluster), data is hash-distributed across all tservers from
the very first write. This converts cold-start throughput from
single-tserver-bound to cluster-wide from block 1.

This applies to all three table types: metadata, tx_status, and
per-namespace state tables (ns_*). The setting auto-detects the DB backend
and is silently ignored on PostgreSQL, which has no tablet concept.

Signed-off-by: Senthilnathan <cendhu@gmail.com>

Pull Request Pull Request #311: [vc] split tables into predefined number of tablets

Coverage Stats

8584 of 10238 relevant lines covered (83.84%)

0.92 hits per line

hyperledger / fabric-x-committer / 21869758251 / 1
89%
main: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job db-test - 21869758251.1

hyperledger / fabric-x-committer / 21869758251 / 1 89% main: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job db-test - 21869758251.1

hyperledger / fabric-x-committer / 21869758251 / 1
89%
main: 92%

README BADGES
x