You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: Implement "BeginStop" asynchronous solution instead of current "Stop" solution. Stop is Synchronous and can take a long time to shutdown concurrent threads, especially if there are a bunch to shutdown.
Not a bug, just a request: When passing jobs to Stop-RSJob, use the asynchronous solution "BeginStop" instead of "Stop", then monitor all jobs until stopped. Once done, return out of Stop-RSJob
Reason for change: Using BeginStop will result in faster shutting down of threads as they will all start shutting down at the same time. This is also helpful from preventing pending jobs from starting, which looks like could happen.
BeginStop returns an Async handle that will need to be monitored for completion, but all handles can be monitored until Handle.IsCompleted is true.
The text was updated successfully, but these errors were encountered:
MVKozlov
added a commit
to MVKozlov/PoshRSJob
that referenced
this issue
Dec 27, 2018
Move completed job data receiving into private function
give Receive-RSJob a chance to receive data (there was race condition possible)
Implemented proxb#193
Feature request: Implement "BeginStop" asynchronous solution instead of current "Stop" solution. Stop is Synchronous and can take a long time to shutdown concurrent threads, especially if there are a bunch to shutdown.
Not a bug, just a request: When passing jobs to Stop-RSJob, use the asynchronous solution "BeginStop" instead of "Stop", then monitor all jobs until stopped. Once done, return out of Stop-RSJob
Reason for change: Using BeginStop will result in faster shutting down of threads as they will all start shutting down at the same time. This is also helpful from preventing pending jobs from starting, which looks like could happen.
BeginStop returns an Async handle that will need to be monitored for completion, but all handles can be monitored until Handle.IsCompleted is true.
The text was updated successfully, but these errors were encountered: