-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weave as a background service #136
Merged
Merged
Conversation
This file contains 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
This was referenced May 16, 2020
3 tasks
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.
This is an experimental implementation of #132
Direct link to the readme: https://github.com/mratsim/weave/tree/8f9db32b71cb1e493c496d8afce44aba38f9d6c6#foreign-thread--background-service-experimental
Weave can now be started in a dedicated thread via
runInBackground(Weave)
.Jobs can be submitted to it and waited upon with
submit fnCall(args)
andwaitFor(Pending)
.To do that, a thread (unmanaged by Weave) must call
setupSubmitterThread(Weave)
and thenwaitUntilReady(Weave)
.A job is different from a task in only small ways.
when a job enters the runtime, work on a new job will wait for all subtasks to be processed unless the job does not spawn enough tasks to create work for all CPUs.
To ensure proper usage of
submit
/waitFor
on submitter threads andspawn
/sync
within Weave tasks a distinctPending
type has been created with the same semantics asFlowvar
.In the future,
submit
/waitFor
may be removed for an unifiedspawn
/sync
construct.