Add a pony primitive that exposes scheduler information #3984
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.
Previously, when users wanted to optimize the parallelizing work based on the maximum number of actors that can be run at a single time, we were pointing them to using the private runtime method
@ponyint_sched_cores()
.This was problematic for two reasons:
We've now exposed some information about scheduler threads via a new package
runtime_info
thereby resolving both of the problems mentioned above.Pony users should expect to see additional information added to the
runtime_info
package moving forward.Anyone who was using the internal
ponyint_sched_cores()
FFI call will need to update to usingruntime_info
asponyint_sched_cores()
has been removed.Closes #3985