Bound paged retrieval responses
This commit is contained in:
parent
176b2d2784
commit
529accf858
15 changed files with 1567 additions and 30 deletions
|
|
@ -45,3 +45,12 @@ operations fail if they load a complete project, parse source files, reconstruct
|
|||
projection, extract adapter sources, build an index, prepare a render, construct rendered output,
|
||||
or hash complete rendered output. Its latency ceilings are the Milestone 1 targets, not claims
|
||||
about all hardware.
|
||||
|
||||
Every warmup and measured invocation is validated. The recorded counter ranges also require one
|
||||
index synchronization for the synchronization operation, no hidden synchronization for reads and
|
||||
status, one index check for each retrieval snapshot, and exactly one manager request for viewer
|
||||
status. The 1,000-node run records bounded semantic summaries for exact errors, search, filtering,
|
||||
backlinks, both traversal directions, paged context, render receipt states, and visualization
|
||||
freshness. The reported p95 uses the nearest-rank method; with ten samples it is the maximum.
|
||||
`process_peak_rss_kib` is the cumulative main-process `RUSAGE_SELF` high-water mark and excludes the
|
||||
detached viewer worker.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue