Skip to content

Unify SurrealDB benchmark target and endpoints, and fix sync mode#226

Merged
tobiemh merged 5 commits intomainfrom
feature/unify-surrealdb-endpoints
Apr 19, 2026
Merged

Unify SurrealDB benchmark target and endpoints, and fix sync mode#226
tobiemh merged 5 commits intomainfrom
feature/unify-surrealdb-endpoints

Conversation

@tobiemh
Copy link
Copy Markdown
Member

@tobiemh tobiemh commented Apr 18, 2026

  • Single SurrealDB endpoint implementation with docker/embedded/remote endpoint parsing
  • Ensures durable transaction writes are correctly configurable. Previously SurrealDB was always using sync writes, even when disabled in the benchmarking script.

tobiemh added 5 commits April 18, 2026 20:16
- Single SurrealDB DatabaseKind with server:/embedded/remote endpoint parsing
- Trim database enum and simplify wiring in database.rs/main.rs
- Align run.sh benchmark matrix and SurrealDB-related flags
- Document unified usage in README
- Update CI workflow for the new SurrealDB target/endpoints
The retry helper in the fulltext index cleanup path only matched the
executor-level "The query was not executed due to a failed transaction"
wrapper. For single-statement queries like REMOVE INDEX / REMOVE ANALYZER
the raw kvs TransactionConflict error surfaces directly, so the retry
never kicked in and the benchmark failed on transient RocksDB conflicts.
Match on "This transaction can be retried" as well so both shapes are
handled.
Re-enables the previously skipped SurrealDB + SurrealKV benchmark matrix
entry, and lowers the per-benchmark thread count from 48 to 4 across the
CI run matrix to better reflect available CI runner resources.
Inline CRUD_BENCH_SCANS alongside CRUD_BENCH_BATCHES so the CI
exercises count/limit/offset scans plus indexed equality, range
and fulltext conditions against every matrix database.
@tobiemh tobiemh merged commit 477b396 into main Apr 19, 2026
37 of 38 checks passed
@tobiemh tobiemh deleted the feature/unify-surrealdb-endpoints branch April 19, 2026 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant