-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[RFC] 0014 Task Workers #897
base: main
Are you sure you want to change the base?
Conversation
3f4640a
to
025954c
Compare
Implementing SAP/ui5-tooling#897 Based on SAP/ui5-builder#955
Implementing SAP/ui5-tooling#897 Based on #955
rfcs/0014-task-workers.md
Outdated
``` | ||
|
||
**TODO:** Decide on configuration style. Option 1 does not allow for introducing additional per-processor configuration in the future (e.g. max CPU threads, priority, etc.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find option 3 the most consistent one, as it has a very similar structure as the task itself, and order does not matter (right?), so there's no reason for option 2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree and updated that part
Concept for a new API provided to UI5 Tooling build tasks, enabling easy use of Node.js Worker Threads to execute CPU intensive operations outside of the main thread.
View rendered version
PoC: SAP/ui5-builder#955
JIRA: CPOUI5FOUNDATION-751