Profile ORM queries against bounded table windows (#52) #64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/issue52-orm-query-profile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Direct ORM paging is not a drop-in replacement for the current backend-query plus bounded live window: query semantics differ, and direct ordering blocks the renderer on a large graph. Add a reproducible diagnostic, API/semantics audit and raw measurements without changing production query behavior.
Updated against current main, resolving the package script conflict after the experimental-app move. Add
pnpm typecheck:orm-queryfor repeatable helper validation. Preserve the original 21 October evidence and add fresh 28 October cloud samples with their host/measurement limitations.Current validation:
Ready for review as the completed profiling investigation. Related to #52; deliberately leaves that issue open for query latency, membership/search costs, renderer blocking and representative performance acceptance evidence. This PR does not claim to solve those performance requirements.
WIP: Profile ORM queries against bounded table windows (#52)to Profile ORM queries against bounded table windows (#52)