<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Runspace on MXI</title><link>https://mxii.eu.org/tags/runspace/</link><description>Recent content in Runspace on MXI</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 16 Sep 2016 21:05:05 +0300</lastBuildDate><atom:link href="https://mxii.eu.org/tags/runspace/index.xml" rel="self" type="application/rss+xml"/><item><title>Parallel processing in PowerShell</title><link>https://mxii.eu.org/2016/09/16/parallel-processing-in-powershell/</link><pubDate>Fri, 16 Sep 2016 21:05:05 +0300</pubDate><guid>https://mxii.eu.org/2016/09/16/parallel-processing-in-powershell/</guid><description>&lt;p>Running arbitrary number of tasks in parallel with PowerShell, while showing overall progress.&lt;/p>
&lt;p>The main disadvantage of the code I provided in &lt;a href="https://mxii.eu.org/2016/08/17/blog-minification-in-a-fancy-way-with-powershell/">previous post&lt;/a> is that it is performed sequentially. We can speed it up by means of parallel processing, since main limiting factor is not an I/O but minifying algorithms performance.&lt;/p>
&lt;p>There are a lot of ways to use parallelism in PowerShell and it wasn&amp;rsquo;t clear for me which one suits well for my task. I.e. to convert my script, which is processing a lot of small files on a local machine.&lt;/p>
&lt;p>It also should:&lt;/p>
&lt;ul>
&lt;li>provide updates in real time;&lt;/li>
&lt;li>keep output table formatting as close to original as possible.&lt;/li>
&lt;/ul></description></item></channel></rss>