Files
jobtrackingapp/docs/performance/USER_LIST_PROJECTION_PLAN.md
T

2.5 KiB

User-list projection implementation plan

Existing isolated codex/perf-mariadb-qualification, source63db9c8a; relevant API/test baseline equivalent to A3 1ec15429. Owner PERF-01 instructions authorise bounded measured projections while keeping pagination separately open. Sequential root execution: parallel worker quota was unavailable; no competing mutable environment.

Goal: stop loading full CV, avatar, credentials and account integration state for the existing admin summary response. Existing two-query batching is retained. Use EF's ordinary projection into the existing summary inputs; no cache, schema, new DTO, route, package or UI control.

Reach: UsersController.List production context branch; ToDto's ten required user fields; existing UsersControllerTests relational query counter and representative user fixture. Existing legacy/manual-construction branch and all create/role/reset/delete callers retain signatures and semantics. AdminUsersPage remains unchanged and still receives the complete ordered list. This is not completion of PERF11 paging.

Alternatives considered: server pagination would require coordinated DataGrid filtering/sorting/mobile navigation and is larger; restricting fields in SQL immediately removes unnecessary large data while preserving compatibility. Returning fewer DTO fields would break consumers and is rejected.

  • Extend existing relational test with large synthetic CV/profile/avatar and credential fields, all summary fields, last-admin/current-user/role assertions, actual selected-column capture and no tracking. Run unchanged application and retain expected projection failure.
  • Add only the ten ToDto input fields to the production EF Select. Re-run all UsersControllerTests and relevant existing identity/ownership tests. Measure actual selected fields and excluded synthetic text bytes, without inferring network payload or latency gains.
  • Review SQL translation/safety, source-bound evidence, AST refresh, commit and publish; integrate only validated change into A3 and update central TODO/status/checkpoint. Native MariaDB execution remains separate unless run on this exact projection.

Review focus: null summary values; linked Google timestamp; current/last-admin safety and arbitrary role preservation; no extra identity role calls or tracked partial user entities; stable existing email ordering/full result count. Existing tests cover manual fallback and mutation safeguards. Rollback is the Select removal; no data rollback. All formal roadmap/security/release gates remain.