Timing a command s execution in PowerShell

Question

Is there a simple way to time the execution of a command in PowerShell  like the  time  command in Linux  I came up with this    s Get-Date    do something ps1    e Get-Date    e -  s  TotalSeconds   But I would like something simpler like  time   do something ps1

User · Answer

You can also get the last command from history and subtract its EndExecutionTime from its StartExecutionTime     do something ps1    command   Get-History -Count 1    command EndExecutionTime -  command StartExecutionTime

User · Answer

Here s a function I wrote which works similarly to the Unix time command   function time       Param           Parameter Mandatory  true            string  command           switch  quiet    false            start   Get-Date     try           if   -not  quiet                 iex  command   Write-Host           else               iex  command  gt   null                 finally             Get-Date  -  start           Source  https   gist github com bender-the-greatest 741f696d965ed9728dc6287bdd336874

User · Answer

Simples  function time  block         sw    Diagnostics Stopwatch   StartNew        amp  block      sw Stop        sw Elapsed     then can use as  time     some command     You may want to tweak the output

User · Answer

Yup   Measure-Command     do something ps1     Note that one minor downside of Measure-Command is that you see no stdout output      Update  thanks to  JasonMArcher  You can fix that by piping the command output to some commandlet that writes to the host  e g  Out-Default so it becomes   Measure-Command     do something ps1   Out-Default     Another way to see the output would be to use the  NET Stopwatch class like this    sw    Diagnostics Stopwatch   StartNew     do something ps1  sw Stop    sw Elapsed

User · Answer

Use Measure-Command  Example  Measure-Command    lt your command here gt    Out-Host     The pipe to Out-Host allows you to see the output of the command  which is otherwise consumed by Measure-Command

User · Answer

Just a word on drawing  incorrect  conclusions from any of the performance measurement commands referred to in the answers  There are a number of pitfalls that should taken in consideration aside from looking to the bare invocation time of a  custom  function or command   Sjoemelsoftware      Sjoemelsoftware  voted Dutch word of the year 2015   Sjoemelen means cheating  and the word sjoemelsoftware came into being due to the Volkswagen emissions scandal  The official definition is  software used to influence test results     Personally  I think that  Sjoemelsoftware  is not always deliberately created to cheat test results but might originate from accommodating practical situation that are similar to test cases as shown below   As an example  using the listed performance measurement commands  Language Integrated Query  LINQ  1   is often qualified as the fasted way to get something done and it often is  but certainly not always  Anybody who measures a speed increase of a factor 40 or more in comparison with native PowerShell commands  is probably incorrectly measuring or drawing an incorrect conclusion   The point is that some  Net classes  like LINQ  using a lazy evaluation  also referred to as deferred execution 2    Meaning that when assign an expression to a variable  it almost immediately appears to be done but in fact it didn t process anything yet     Let presume that you dot-source your     Dosomething ps1 command which has either a PowerShell or a more sophisticated Linq expression  for the ease of explanation  I have directly embedded the expressions directly into the Measure-Command     Data     1  100000  ForEach  PSCustomObject   Index    Property  Get-Random      Measure-Command        PowerShell    Data Where    Index -eq 12345     totalmilliseconds 864 5237   Measure-Command        Linq    Linq Enumerable   Where  Data   Func object bool     param  Item   Return  Item Index -eq 12345      totalmilliseconds 24 5949   The result appears obvious  the later Linq command is a about 40 times faster than the first PowerShell command  Unfortunately  it is not that simple     Let s display the results   PS C   gt   PowerShell  Index  Property -----  -------- 12345 104123841  PS C   gt   Linq  Index  Property -----  -------- 12345 104123841   As expected  the results are the same but if you have paid close attention  you will have noticed that it took a lot longer to display the  Linq results then the  PowerShell results  Let s specifically measure that by just retrieving a property of the resulted object   PS C   gt   Measure-Command   PowerShell Property   totalmilliseconds 14 8798 PS C   gt   Measure-Command   Linq Property   totalmilliseconds 1360 9435   It took about a factor 90 longer to retrieve a property of the  Linq object then the  PowerShell object and that was just a single object   Also notice an other pitfall that if you do it again  certain steps might appear a lot faster then before  this is because some of the expressions have been cached   Bottom line  if you want to compare the performance between two functions  you will need to implement them in your used case  start with a fresh PowerShell session and base your conclusion on the actual performance of the complete solution    1  For more background and examples on PowerShell and LINQ  I recommend tihis site  High Performance PowerShell with LINQ  2  I think there is a minor difference between the two concepts as with lazy evaluation the result is calculated when needed as apposed to deferred execution were the result is calculated when the system is idle

User · Answer

Using Stopwatch and formatting elapsed time   Function FormatElapsedTime  ts          elapsedTime           if    ts Minutes -gt 0                  elapsedTime    string   Format    0 00  min   1 00   2 00  sec     ts Minutes   ts Seconds   ts Milliseconds   10              else                elapsedTime    string   Format    0 00   1 00  sec     ts Seconds   ts Milliseconds   10               if   ts Hours -eq 0 -and  ts Minutes -eq 0 -and  ts Seconds -eq 0                 elapsedTime    string   Format   0 00  ms     ts Milliseconds              if   ts Milliseconds -eq 0                 elapsedTime    string   Format   0  ms    ts TotalMilliseconds              return  elapsedTime    Function StepTimeBlock  step   block         Write-Host   r n           Write-Host  step     Write-Host   r n             sw    Diagnostics Stopwatch   StartNew        amp  block      sw Stop        time    sw Elapsed       formatTime   FormatElapsedTime  time     Write-Host   r n t      gt   step took  formatTime      Usage Samples  StepTimeBlock   Publish  0  Reports  -f  Script ArrayReportsList Count           Script ArrayReportsList       Publish-Report  WebServiceSSRSRDL     CarpetaReports  CarpetaDataSources  Script datasourceReport       StepTimeBlock   My Process         do something ps1

[powershell] Timing a command's execution in PowerShell

Examples related to powershell

Examples related to time

Examples related to performance-testing