[PowerShell] Lower Memory Consumption When using "cmd /c" instead of ".\" to run exe?

[+Red King Subscriber²]

I don't get this,

cmd /c " `"mysqldump.exe`" .. > $foo "
# vs
.\mysqldump.exe .. > $foo

PS process eats all my memory when using .\foobar.exe whereas going using cmd /c "foobar.exe" does not.

 

 

What the ###### is happening here? Ideas?

[+rdlenk Subscriber²]

Does the effect change at all if you use Start-Process?

[+Red King Subscriber²]

  On 11/08/2016 at 16:55, rdlenk said:

Does the effect change at all if you use Start-Process?

Expand  

I think that did the trick! I think PS tried storing the file in memory before writing it to disk with the ">" op,

With Start-Process and -RedirectStandardOutput - it does not try to store the file in memory.

 

[+rdlenk Subscriber²]

I don't think PowerShell likes using ">" anyways. Should be something like "<command> | Write-Output <filename>" or something like that.

[+Red King Subscriber²]

I need some follow up tips.

 

I noticed that Start-Process executes slower than "cmd /c" - any reason for that?

[+Red King Subscriber²]

  On 30/08/2017 at 12:47, Riva said:

In both scenarios foobar.exe is a child process of either powershell or cmd instance. Powershell is a managed process (.NET CLR) vs. CMD which is native app. Native apps have a lighter footprint and higher processor resolution. .NET CLR (and Java) tend to use a virtualised CPU in order to ensure type safety. .NET native solves this problem but it isnt as widely implemented yet.

 

Expand  

I don't think that explains it. I mean there is a difference between native and .NET but its minor for non-performance critical code. Like Start-Process just executes another executable and waits for it - so not much runs in .NET CLR anyway here.

 

As far as I remember (this topic is from a year ago and I don't work there anymore) - it just did nothing for a much longer time when launching from Start-Process versus indirectly through CMD. Like it wasn't an issue with higher process utilization - mysqldump through Start-Process was simply doing ######-all for a long time.