Erik JohnstonandClaude Fable 5.1 eeb74db0aa Cache events on the Rust state resolution handler ...

Loading and parsing events was most of a Rust resolution's time: against
a warm Python event cache, Rust was level with Python. The handler now
keeps the events it loads, keyed by event ID, so a resolution in a room
it has seen reads them from memory.

The conflict cache's LRU becomes a generic SizedLru shared by both
caches. The Postgres store takes the event cache, reads it before the
database and inserts what it loads. The stats report event cache hits
and the time spent converting state to and from Python.

Invalidation follows the Python event cache rather than having its own
sources: EventsWorkerStore._invalidate_local_get_event_cache and the
room-wide variant drop the same events from the Rust cache. Those two
methods are where every event cache invalidation ends up, including a
partial-state event's rejection status changing, which is the one
change state resolution can observe.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ULdieJyQoHNzeHq42H2M1p

2026-10-13 16:04:19 +00:00

..

benches

Add push rules for MSC4075: MatrixRTC invites and notifications (#20227)

2026-09-25 10:40:24 +00:00

src

Cache events on the Rust state resolution handler

2026-10-13 16:04:19 +00:00

build.rs

resolves #19403 Report the rust compiler version used in the prometheus metrics (#19643)

2026-04-03 11:21:23 +02:00

Cargo.toml

Add a connection-checkout timeout to the native Rust Postgres pool

2026-10-12 18:31:24 +00:00

clippy.toml

Move per-homeserver Rust state into a RustRuntime object on the HomeServer (#20011)

2026-09-21 18:48:37 +01:00