Skip to content

hls graph runtime engine experiment#4927

Draft
soulomoon wants to merge 38 commits into
haskell:masterfrom
soulomoon:codex/hls-graph-runtime-engine
Draft

hls graph runtime engine experiment#4927
soulomoon wants to merge 38 commits into
haskell:masterfrom
soulomoon:codex/hls-graph-runtime-engine

Conversation

@soulomoon
Copy link
Copy Markdown
Collaborator

@soulomoon soulomoon commented May 6, 2026

WIP/experimental

@soulomoon soulomoon requested review from fendor and wz1000 as code owners May 6, 2026 13:22
@soulomoon soulomoon marked this pull request as draft May 6, 2026 13:24
@soulomoon soulomoon added the performance Issues about memory consumption, responsiveness, etc. label May 6, 2026
@soulomoon soulomoon changed the title Codex/hls graph runtime engine hls graph runtime engine May 6, 2026
@soulomoon soulomoon changed the title hls graph runtime engine hls graph runtime engine experiment May 6, 2026
@soulomoon
Copy link
Copy Markdown
Collaborator Author

soulomoon commented May 12, 2026

Here is the main hls-graph changes we talked about. @fendor

hls-graph now has an explicit runtime engine for running actions, tracking runtime dependencies, and restarting selectively.

The benchmark shows the intended tradeoff. Startup improves broadly, mostly around 25-32%, from skipping kills for non-dirty work. For very short single-edit operations, the central thread maintenance cost is visible in userT / totalT, so some “after edit” cases regress. In the typing-burst cases, which better match human editing, that overhead is amortized and is partly offset by avoiding unnecessary non-dirty kills.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

performance Issues about memory consumption, responsiveness, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant