stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Precompress the immutable dashboard runtime to preserve request responsiveness #431

New Issue
Closed
opened 2026-08-09 22:09:45 +00:00 by timmy · 0 comments
timmy commented 2026-08-09 22:09:45 +00:00
Owner
Copy Link

Problem

The 442 KB fingerprinted browser runtime is gzip-compressed at level 9 on the ASGI event loop for every cold request. Local audit measurements show about 39 ms CPU per request and serialized latency under concurrent cold launches, even though the runtime is immutable and assembled once at startup.

Vertical slice

  • deterministically precompress the content-addressed runtime once during frontend build
  • negotiate gzip directly at the runtime route, with identity and gzip;q=0 preserved
  • bypass runtime middleware recompression while preserving immutable caching, CSP, Vary, and exact content length
  • use a balanced default level for remaining dynamic compression

Acceptance tests

  • identical sources produce byte-identical gzip bytes (mtime=0)
  • gzip clients receive the precomputed representation and exact compressed content length
  • identity and gzip;q=0 clients receive original bytes
  • repeated runtime requests never invoke dynamic gzip compression
  • concurrent runtime cold requests do not serialize compression work and /healthz remains responsive
  • full suite passes

No historical issue or recent commit covers precompression/event-loop responsiveness. Related #417 only introduced HTTP gzip negotiation and transfer-size coverage.

## Problem The 442 KB fingerprinted browser runtime is gzip-compressed at level 9 on the ASGI event loop for every cold request. Local audit measurements show about 39 ms CPU per request and serialized latency under concurrent cold launches, even though the runtime is immutable and assembled once at startup. ## Vertical slice - deterministically precompress the content-addressed runtime once during frontend build - negotiate gzip directly at the runtime route, with identity and `gzip;q=0` preserved - bypass runtime middleware recompression while preserving immutable caching, CSP, `Vary`, and exact content length - use a balanced default level for remaining dynamic compression ## Acceptance tests - identical sources produce byte-identical gzip bytes (`mtime=0`) - gzip clients receive the precomputed representation and exact compressed content length - identity and `gzip;q=0` clients receive original bytes - repeated runtime requests never invoke dynamic gzip compression - concurrent runtime cold requests do not serialize compression work and `/healthz` remains responsive - full suite passes No historical issue or recent commit covers precompression/event-loop responsiveness. Related #417 only introduced HTTP gzip negotiation and transfer-size coverage.
timmy self-assigned this 2026-08-09 22:09:45 +00:00
timmy closed this issue 2026-08-09 22:22:04 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
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: stackchain/stackchain-dashboard#431
No description provided.
Delete Branch "%!s()"

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?