Process left running

Sep 28, 2013 at 2:35 PM
Don't forget to do an $AsyncPipeline.Close() after you've finished with it. Otherwise it leaves PowerShell v3 ISE running in Task Manager even after you exit.

It works pretty well. I've been running a thread pool of 20 tasks in parallel. The difference from Start-Job is 2GB memory (and two dozen processes) vs 500MB memory (and a single process). They also run something on the order of ten times faster; I didn't need to measure it.

The module isn't really finished yet. The syntax could live with being a bit closer to the traditional Job syntax - adding identifiers to the threads so they can be retrieved and removed individually instead of all together as a set. But it's no big deal.