PERF: Settings rule 1 — serve interactive reads from committed precomputed projections (#663) #690

New issue

Open

opened 2026-10-02 05:36:42 +00:00 by kayg · 0 comments

kayg commented

2026-10-02 05:36:42 +00:00

Owner

Context: #663 matrix and DESIGN §58 rule 1. Scope: Settings must serve interactive reads from committed precomputed projections. Shared client machinery belongs only to #665–#668.

Evidence at c4a61e8cf0:

Endpoint: GET /api/v1/appearance.
Source: crates/calternal-server/src/appearance.rs:739. Reads and projects settings.json on a UI read. Auth/security reads use SQLite, but not all Settings cards use a precomputed Index projection.
Representative endpoint numbers, server/client revisions, fixture size, lock/HDD qualification and limits are in the #663 production/HDD table. Those numbers do not prove this rule passes; the structural gap above is separate evidence.

Expected and regression tests:
Hold a plugin writer/indexer transaction during reads; GET returns the last complete committed projection through the WAL reader pool. Instrument external-call/file-read/parse counts and require zero on a warm UI read. Prove changed input is indexed before its new revision is published; queued provider side effects reconcile after reconnect/restart. Test a cold Index rebuild, concurrent source edits, deleted items and two-User/share isolation. Source files and authoritative security state keep their DESIGN ownership.

Performance test:
Extend the existing bench profile for this hot path and the #549/#641 harness. Use production builds on root@10.69.69.63, bench/hdd-emu.sh and flock -w 14400 /root/perf.lock. Record load inside the lock; ≥5 samples, median/p95/max, average CPU/RSS and one realistic large-data/burst case. Separate warm, cold, accepted and durable boundaries. First usable 10k view ≤1.5 s; cached open/warm return ≤100 ms and accepted action ≤150 ms where applicable. Compare only a matching baseline in docs/perf/baseline.json; missing profiles require a new recorded baseline, not a made-up comparison.

Reuse/ownership:
Raw configuration and credentials must not enter persistent client caches. Use authorized in-memory/precomputed server projections and keep step-up. Reuse #642 scheduling and safe Resource work.
Reuse #555 userStorage, #549 route caches, Files signed keysets/change feed and the existing Db reader_pool. #641 owns blaze measurements; #642 owns Settings opening; #640 owns Mail layouts; #639 owns linked Note opening. Integrate their active/completed branches before changing related code.

Acceptance:
Existing tests and status expectations stay intact. Run the per-crate gates (and calternal-server for route/contract changes), web gates if changed, and one time-boxed real-server regression/adversarial round for any new API contract. Preserve calternal-fs as the only filesystem interface and the server as the only writer. UI changes need pointer/touch/keyboard/screen-reader coverage and real-production captures at 390/820/1440 in both themes. Do not change shared motion for keyboard input.

Representative measurement from the audit (not a full-view budget result):
/api/v1/auth/me/security, five serial requests after fixture readiness, all HTTP 200. Median/p95/max 482.2/1266.5/1266.5 ms; five-request burst median/p95/max 86.4/89.9/89.9 ms. Serial window server CPU 290 ms, RSS 511967232 bytes; no ETag on these sampled responses. Load inside lock 3.92/2.18/0.96.
Shared release server source cc25c441b7a974185622a1dee853cf38686d2b67, binary SHA-256 2f3567d91c34839851247bc0acbc25a56aaacd14dca269b8f0342ddf83447ed9; embedded production SPA; Chromium browser on the build host through SSH/HTTPS. Server/Home/Index on perf VM HDD emulator: direct-I/O loop, 8 ms read/write dm-delay, 200 IOPS and 150 MiB/s caps. Every measured phase held flock -w 14400 /root/perf.lock. Qualification QD1 115.3 IOPS/8.028 ms median, QD16 200.7 IOPS/96.993 ms. Fixture: 366 Daily notes, 10,980 Logs, 100 Files/Photos, 20 Notes/Tasks, three Budgets and 100 transactions; Mail empty, Admin one User.
Structural source evidence above is the newer audit base, not the measured binary revision. No claim that these revisions are equivalent. The baseline in docs/perf/baseline.json uses another fixture/build/transport; no regression ratio is valid here. See #663 for matching baseline endpoint values and coverage gaps.

Context: #663 matrix and DESIGN §58 rule 1. Scope: Settings must serve interactive reads from committed precomputed projections. Shared client machinery belongs only to #665–#668. Evidence at c4a61e8cf090170f35b1bed3350d9de20c83ecd5: - Endpoint: `GET /api/v1/appearance`. - Source: `crates/calternal-server/src/appearance.rs:739`. Reads and projects settings.json on a UI read. Auth/security reads use SQLite, but not all Settings cards use a precomputed Index projection. - Representative endpoint numbers, server/client revisions, fixture size, lock/HDD qualification and limits are in the #663 production/HDD table. Those numbers do not prove this rule passes; the structural gap above is separate evidence. Expected and regression tests: Hold a plugin writer/indexer transaction during reads; GET returns the last complete committed projection through the WAL reader pool. Instrument external-call/file-read/parse counts and require zero on a warm UI read. Prove changed input is indexed before its new revision is published; queued provider side effects reconcile after reconnect/restart. Test a cold Index rebuild, concurrent source edits, deleted items and two-User/share isolation. Source files and authoritative security state keep their DESIGN ownership. Performance test: Extend the existing bench profile for this hot path and the #549/#641 harness. Use production builds on root@10.69.69.63, bench/hdd-emu.sh and flock -w 14400 /root/perf.lock. Record load inside the lock; ≥5 samples, median/p95/max, average CPU/RSS and one realistic large-data/burst case. Separate warm, cold, accepted and durable boundaries. First usable 10k view ≤1.5 s; cached open/warm return ≤100 ms and accepted action ≤150 ms where applicable. Compare only a matching baseline in docs/perf/baseline.json; missing profiles require a new recorded baseline, not a made-up comparison. Reuse/ownership: Raw configuration and credentials must not enter persistent client caches. Use authorized in-memory/precomputed server projections and keep step-up. Reuse #642 scheduling and safe Resource work. Reuse #555 userStorage, #549 route caches, Files signed keysets/change feed and the existing Db reader_pool. #641 owns blaze measurements; #642 owns Settings opening; #640 owns Mail layouts; #639 owns linked Note opening. Integrate their active/completed branches before changing related code. Acceptance: Existing tests and status expectations stay intact. Run the per-crate gates (and calternal-server for route/contract changes), web gates if changed, and one time-boxed real-server regression/adversarial round for any new API contract. Preserve calternal-fs as the only filesystem interface and the server as the only writer. UI changes need pointer/touch/keyboard/screen-reader coverage and real-production captures at 390/820/1440 in both themes. Do not change shared motion for keyboard input. Representative measurement from the audit (not a full-view budget result): `/api/v1/auth/me/security`, five serial requests after fixture readiness, all HTTP 200. Median/p95/max 482.2/1266.5/1266.5 ms; five-request burst median/p95/max 86.4/89.9/89.9 ms. Serial window server CPU 290 ms, RSS 511967232 bytes; no ETag on these sampled responses. Load inside lock 3.92/2.18/0.96. Shared release server source `cc25c441b7a974185622a1dee853cf38686d2b67`, binary SHA-256 `2f3567d91c34839851247bc0acbc25a56aaacd14dca269b8f0342ddf83447ed9`; embedded production SPA; Chromium browser on the build host through SSH/HTTPS. Server/Home/Index on perf VM HDD emulator: direct-I/O loop, 8 ms read/write dm-delay, 200 IOPS and 150 MiB/s caps. Every measured phase held `flock -w 14400 /root/perf.lock`. Qualification QD1 115.3 IOPS/8.028 ms median, QD16 200.7 IOPS/96.993 ms. Fixture: 366 Daily notes, 10,980 Logs, 100 Files/Photos, 20 Notes/Tasks, three Budgets and 100 transactions; Mail empty, Admin one User. Structural source evidence above is the newer audit base, not the measured binary revision. No claim that these revisions are equivalent. The baseline in docs/perf/baseline.json uses another fixture/build/transport; no regression ratio is valid here. See #663 for matching baseline endpoint values and coverage gaps.

kayg referenced this issue

2026-10-02 05:46:53 +00:00

PERF: instant everywhere — app-wide speed architecture rules, audit and shared primitives #663

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

kayg/calternal#690

No description provided.

Rows
Columns