Skip to content

chore(deps): bump es-entity to 0.11.11 - #791

Merged
nicolasburtey merged 4 commits into
mainfrom
chore/bump-es-entity-0.11.11
Jul 30, 2026
Merged

chore(deps): bump es-entity to 0.11.11#791
nicolasburtey merged 4 commits into
mainfrom
chore/bump-es-entity-0.11.11

Conversation

@nicolasburtey

Copy link
Copy Markdown
Member

Bumps es-entity 0.11.9 → 0.11.11 (GaloyMoney/es-entity#168).

es-entity 0.11.11 gates the sargable multi-filter query matrix (added in the 0.11.9 series) behind an opt-in per-repo #[es_repo(..., sargable_filters)] attribute, defaulting to off. This is the rebuild-against-new-es-entity step of the release chain; cala's own EsRepo repos will emit the catch-all COALESCE query for the multi-filter case unless a repo explicitly opts in. Backward compatible, no source changes needed.

Rebuild against es-entity 0.11.11 (GaloyMoney/es-entity#168), which gates
the sargable multi-filter query matrix behind an opt-in per-repo
attribute (default off). Backward compatible; cala's EsRepo repos emit
the catch-all COALESCE query for the multi-filter case unless a repo opts
in with #[es_repo(..., sargable_filters)].
@github-actions

github-actions Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

📊 Performance Report

Commit: 9b68fb1
Updated: 2026-07-30 19:44:46 UTC

Cala Performance Benchmark Results (non-representative)

Criterion Benchmark Results (single-threaded)

Benchmark Time per Run Throughput % vs Baseline
post_simple_transaction 4.268ms 234 tx/s 0 (baseline)
post_and_recalculate_ec_account_set 11.470ms 87 tx/s -168.0%
post_and_batch_recalculate_ec_account_set 9.168ms 109 tx/s -114.0%
post_multi_layer_transaction 7.639ms 130 tx/s -78.0%
post_simple_transaction_with_effective_balances 6.695ms 149 tx/s -56.0%
post_simple_transaction_with_skipped_velocity 3.842ms 260 tx/s +9.0%
post_simple_transaction_with_velocity 4.593ms 217 tx/s -7.0%
post_simple_transaction_with_hit_velocity 2.182ms 458 tx/s +48.0%
post_simple_transaction_with_one_account_set 5.575ms 179 tx/s -30.0%
post_simple_transaction_with_five_account_sets 8.152ms 122 tx/s -90.0%
post_simple_transaction_with_ec_account_set 3.929ms 254 tx/s +7.0%

Load Testing Results (parallel-execution)

Scenario tx/s
1 parallel 152.47
2 parallel 209.32
5 parallel 230.93
10 parallel 261.11
20 parallel 276.31
2 contention 156.24
5 contention 187.68
2 acct_sets 137.22
5 acct_sets 167.52

Note: Performance results may vary based on system resources and database state.

Last updated by commit 9b68fb1

…0.11.11

es-entity 0.11.11 gates the sargable multi-filter query matrix behind an
opt-in per-repo attribute (default off), so the EsRepo derive now emits a
different (smaller) set of list queries. The committed .sqlx cache (built
against es-entity 0.11.9) and the job 0.6.35 dependency both carried stale
query hashes, causing offline builds to fail with:

  error: `SQLX_OFFLINE=true` but there is no cached data for this query

- bump job 0.6.35 -> 0.6.36 (rebuilt against es-entity 0.11.11)
- regenerate cala-ledger/.sqlx via `cargo sqlx prepare -- --all-features`
… lint)

Rust 1.93 clippy (stable toolchain) flags .err().expect() as err_expect;
the workspace-clippy check runs with --deny warnings, so resolve the two
pre-existing occurrences in account_set tests.
job 0.6.36 modified the released 20250904065521_job_setup.sql migration
(added autovacuum_vacuum_cost_delay = 0 to unthrottle autovacuum on
job_executions). cala vendors this migration so its own sqlx::migrate!()
is self-contained, but job 0.6.36 also runs its migrator against the same
DB. With cala still on the old checksum and job on the new one, the second
migrator fails:

  Error: migration 20250904065521 was previously applied but has been modified

Sync cala-ledger/migrations/20250904065521_job_setup.sql to match job 0.6.36
exactly.
@nicolasburtey
nicolasburtey merged commit c5ac770 into main Jul 30, 2026
5 checks passed
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