Closed psprint closed 1 year ago
I've updated the PR to check if there are any more tasks and schedule for 10s if not.
Stupid question: is this running forever? If so: why? Can't it be stoped once all tasks have been run (and restarted, if there every comes in a new task)?
They run forever because it's ~5 lines of code every 1 second. That's very low overhead. More, if load'' and unload'' ices been passed, then the background schedule calls are needed to test them.
On Thu, 3 Nov 2022 at 11:30, Jan Katins @.***> wrote:
Stupid question: is this running forever? If so: why? Can't it be stoped once all tasks have been run (and restarted, if there every comes in a new task)?
— Reply to this email directly, view it on GitHub https://github.com/zdharma-continuum/zinit/pull/409#issuecomment-1301965993, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOE4CA6R4HMXK3Z7COM7C3WGOO4XANCNFSM6AAAAAARV57JGQ . You are receiving this because you authored the thread.Message ID: @.***>
-- Best regards, Sebastian Gniazdowski
I've added short-circuit return if no tasks, so basically it's 1 line of code every 10 seconds if no tasks.
This breaks the wait
ice.
:tada: This PR is included in version 3.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Description
Change the time interval for the scheduler to check for queued tasks to ten seconds.
Motivation and Context
Lower system resource usage.
Related Issue(s)
362
How Has This Been Tested?
Types of change
Checklist: