Set max thread priority for local-sync #104
Merged
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.
Fixes #103.
Description
localsync thread is important and should run at exact intervals. To ensure this its priority is set to max. Priority setting if fails is ignored for now which means if thread_priority can't set it to max then all can be done is log it. Scheduling behaviour is dependant on the underlying OS. It is user's responsiblity to make sure that program can set thread/process priority. For example on linux you'd have to allow
cpu cpuset
cgroup for current user.This PR has: