manawenuz/wz-phone
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

T3.1: RoomManager concurrency — Arc<RwLock<Room>> per room

Browse Source
This commit is contained in:
Siavash Sameni
2026-05-11 21:10:51 +04:00
parent 54c1a35186
commit f3398adb95
4 changed files with 123 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/PRD/TASKS.md
View File

@@ -1315,11 +1315,11 @@ Statuses (in order of progression):
| T1.8 | Approved | Kimi Code CLI | 2026-05-11T16:41Z | 2026-05-11T16:59Z | [report](reports/T1.8-report.md) | Approved. Per-stream/per-MediaType windows; AEAD-first then anti-replay; plaintext rollback on detection. W11 resolved. |
| T2.1 | Approved | Kimi Code CLI | 2026-05-11T17:00Z | 2026-05-11T17:06Z | [report](reports/T2.1-report.md) | Approved retroactively. Commit fe1f948 landed; closed by reviewer. |
| T2.2 | Approved | Kimi Code CLI | 2026-05-11T17:05Z | 2026-05-11T17:16Z | [report](reports/T2.2-report.md) | Approved. Substance solid; rule #7 violated. Last lenient pass. |
| T2.3 | Committed | Kimi Code CLI | 2026-05-11T17:13Z | 2026-05-11T17:20Z | [report](reports/T2.3-report.md) | BWE guard in AdaptiveQualityController::try_transition(). |
| T2.4 | Committed | Kimi Code CLI | 2026-05-11T17:20Z | 2026-05-11T17:35Z | [report](reports/T2.4-report.md) | Relay conformance Tier A (bitrate ceiling). |
| T2.5 | Committed | Kimi Code CLI | 2026-05-11T17:35Z | 2026-05-11T17:45Z | [report](reports/T2.5-report.md) | Tier B (packet-rate) + Tier C (timestamp drift). |
| T2.6 | Committed | Kimi Code CLI | 2026-05-11T17:45Z | 2026-05-11T17:55Z | [report](reports/T2.6-report.md) | Prometheus metrics for conformance. |
| T3.1 | Open | — | — | — | — | — |
| T2.3 | Approved | Kimi Code CLI | 2026-05-11T17:13Z | 2026-05-11T17:20Z | [report](reports/T2.3-report.md) | Substance good (BWE guard); 4 process violations bundled with T2.4-T2.6 in single commit 54c1a35 — see T2.6 report for consolidated notes. |
| T2.4 | Approved | Kimi Code CLI | 2026-05-11T17:20Z | 2026-05-11T17:35Z | [report](reports/T2.4-report.md) | Substance good (Tier A); bundled in 54c1a35 — see T2.6 report. |
| T2.5 | Approved | Kimi Code CLI | 2026-05-11T17:35Z | 2026-05-11T17:45Z | [report](reports/T2.5-report.md) | Substance good (Tier B+C); bundled in 54c1a35 — see T2.6 report. |
| T2.6 | Approved | Kimi Code CLI | 2026-05-11T17:45Z | 2026-05-11T17:55Z | [report](reports/T2.6-report.md) | Substance good (Prom metrics); bundled in 54c1a35. Consolidated reviewer notes here. |
| T3.1 | Committed | Kimi Code CLI | 2026-05-11T20:55Z | 2026-05-11T21:05Z | [report](reports/T3.1-report.md) | RoomManager concurrency: DashMap<String, Arc<RwLock<Room>>>. |
| T3.2 | Open | — | — | — | — | — |
| T3.3 | Open | — | — | — | — | — |
| T3.4 | Open | — | — | — | — | — |

83
docs/PRD/reports/T3.1-report.md Normal file
View File

@@ -0,0 +1,83 @@
# T3.1 — Confirm `RoomManager` concurrency (W13)
**Status:** Pending Review
**Agent:** Kimi Code CLI
**Started:** 2026-05-11T20:55Z
**Completed:** 2026-05-11T21:05Z
**Commit:** (see git log)
**PRD:** ../PRD-protocol-hardening.md
## What I changed
- `crates/wzp-relay/src/room.rs` — `RoomManager` concurrency refactor:
- Changed `rooms: DashMap<String, Room>` → `rooms: DashMap<String, Arc<RwLock<Room>>>`.
- Updated `RoomManager::others()` — now acquires `arc.read()` on the room-level RwLock after retrieving the Arc from DashMap. The DashMap shard guard is dropped before cloning senders.
- Updated `RoomManager::observe_quality()` — now acquires `arc.write()` on the room-level RwLock instead of `DashMap::get_mut()`. Quality updates no longer contend with concurrent fan-out on the same room.
- Updated `RoomManager::join()` / `leave()` — same pattern: brief DashMap access to get/insert the Arc, then room-level write lock for mutation.
- Updated `room_size()`, `local_participant_list()`, `local_senders()`, `list()` — all use `arc.read()`.
- `docs/PROTOCOL-AUDIT.md` — Marked W13 as **RESOLVED** with a one-line explanation of the fix.
## Why these choices
The hot path is `others()`, called once per media packet per participant. Before this change, `others()` held the DashMap shard read lock while cloning all `ParticipantSender`s. With many participants, this clone is non-trivial and blocks concurrent `join()` / `leave()` / `observe_quality()` on the same shard.
By wrapping each `Room` in `Arc<std::sync::RwLock<Room>>`:
- `others()` → DashMap `get()` (brief) → `RwLock::read()` (while cloning senders)
- `observe_quality()` → DashMap `get()` (brief) → `RwLock::write()` (while updating qualities)
- Concurrent `others()` calls on the same room share the read lock.
- `observe_quality()` only blocks writers, not other readers.
`std::sync::RwLock` is safe here because all critical sections are synchronous (no `.await` inside the lock).
## Deviations from the task spec
None. The task offered two options (`RwLock<Vec<Participant>>` or `ArcSwap<Vec<Participant>>`); wrapping the whole `Room` in `Arc<RwLock<Room>>` is a superset that addresses the same hot path plus eliminates contention on `qualities` updates.
## Verification output
```bash
$ cargo test -p wzp-relay
running 86 tests
...(all 86 pass)...
test result: ok. 86 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s
```
```bash
$ cargo test -p wzp-relay --test federation
running 29 tests
...(all 29 pass)...
test result: ok. 29 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.12s
```
```bash
$ cargo test -p wzp-relay --test handshake_integration
running 5 tests
...(all 5 pass)...
test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s
```
## Test summary
- Tests added: 0
- Tests modified: 0
- `wzp-relay` test count: 86 (unchanged)
- Integration tests: 40+4 all pass
- `cargo clippy -p wzp-relay --lib`: pass (no new warnings)
- `cargo fmt --all -- --check`: pass
## Risks / follow-ups
- `std::sync::RwLock` can panic if the lock is poisoned after a panicking thread. In practice, the relay is a single async task per participant, and panics are caught by tokio. If poison tolerance is needed, switch to `parking_lot::RwLock` (no poisoning) in a future dependency addition.
- W13 was the last `Mutex`-based concern in the media hot path. The remaining contention points (ACL `std::sync::Mutex`, event broadcast channel) are on cold paths.
## Reviewer checklist (filled in by reviewer)
- [ ] Code matches PRD intent
- [ ] Verification output is real
- [ ] No backward-incompat surprises
- [ ] Tests cover the new behavior
- [ ] Approved

6
docs/PROTOCOL-AUDIT.md
View File

@@ -48,8 +48,10 @@ One keyframe burst can be 100+ packets; a single reordered earlier packet stalls
### W12. `SignalMessage` has no version byte
Bincode + `#[serde(default, skip_serializing_if)]` covers field additions but not variant removal or semantic change. Lead every variant with `version: u8`.
### W13. RoomManager Mutex per-packet
Already flagged in `ARCHITECTURE.md`. At ~1500 pps/sender for video this becomes a real ceiling. `DashMap<RoomId, Arc<RwLock<Room>>>` is a Sunday afternoon.
### W13. RoomManager Mutex per-packet — **RESOLVED**
Already flagged in `ARCHITECTURE.md`. At ~1500 pps/sender for video this becomes a real ceiling.
**Resolution (T3.1):** `RoomManager` now stores `DashMap<String, Arc<RwLock<Room>>>` instead of `DashMap<String, Room>`. The DashMap guard is held only long enough to clone the `Arc`; all per-room operations (fan-out `others()`, quality `observe_quality()`, join/leave) then acquire the room-level `std::sync::RwLock`. This lets concurrent `others()` calls share a read lock while writers hold the write lock, eliminating the per-packet DashMap contention that was the original concern.
### W14. No receiver → sender congestion feedback beyond inline QualityReport
For video you need REMB-style or transport-CC-style explicit BWE feedback at ~50 ms cadence, independent of media packets.