Repository navigation
docs: what was measured and decided on where bindings run - #190
Merged
Merged
Conversation
Open question 10 said that which requests run in a worker process is open. Step 2 of #184 measured it on LoKI data: one workspace thread by default, worker processes not built for now, and what a worker design would have to respect (the boundary, the rows of one stage in one worker, the cost of a cut across processes). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Member
Author
|
LGTM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Open question 10 of the developer README said that which requests run in a worker process is open. Step 2 of #184 measured it on real LoKI reductions (numbers in a comment on #184). The entry now states the result: bindings run on threads of the workspace's process, one by default, settable per application; worker processes are not built for now; and what a worker design would have to respect if one is built (the boundary between workspace and workers, the rows of one stage in one worker, the cost of reading a cut across processes).
One sentence is my reading, not a decision: that a process which runs without a person, such as the automatic reduction, is the likely first to need worker processes.
🤖 Generated with Claude Code