Skip to content

CedroDB 0.7.0: diagnostics and performance tools

Pre-release
Pre-release

Choose a tag to compare

@uppy19d0 uppy19d0 released this 16 Oct 03:44

CedroDB 0.7 helps applications inspect local database work: see collection/index inventory, inspect session counters, and execute queries or hybrid retrieval with their actual plans and native timings.

  • Database.diagnostics() reports content limits, collection/index counts, handle health, and bounded query/search/shared-commit counters without document values.
  • Rust profile_query / profile_search, Node profileQuery / profileSearch, and Python profile_query / profile_search execute once and return the ordinary page plus native elapsed microseconds and actual candidate/scanned/returned counts.
  • Python includes python -m cedrodb doctor and an isolated synthetic benchmark command. The benchmark checks result equality, measures scan/index variants, records empirical latency summaries, batch writes, index construction and reopening, and opens no application database.
  • Native SDK examples demonstrate inspection, periodic application-managed logging and index comparisons. Installation documentation explains OS/CPU/libc requirements, virtual environments and native verification.
  • Added a CI gate that rebuilds and tests the standalone Python source archive, including CLI subprocesses using the isolated rebuilt wheel.

The transaction log and backup formats are unchanged. Session metrics reset on reopen; they do not track every public API or external model/tool call. Commit counters include nonempty shared-commit attempts and exclude earlier validation failures/conflicts/no-ops. Timers add overhead; counters do not provide histograms or process RSS. Profiling executes actual work and may traverse additional candidates to count a keyset range.

Validation: 113 Rust, 70 Node and 70 Python tests, native Node/Python interoperability, strict TypeScript fixtures, and the release CI across Linux, macOS ARM64/Intel and Windows. Binaries and source archives are copied from the successful CI artifact; checksums accompany each archive.

This remains an experimental 0.x release. The exact retrieval engine scans RAM-resident records; these tools do not establish production readiness, model quality or superiority over other databases.

Installation · Performance contracts · Benchmark methodology · Portfolio