Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Measure-Command

Updated: October 17, 2013

Applies To: Windows PowerShell 4.0

Measure-Command

Measures the time it takes to run script blocks and cmdlets.

Syntax

Parameter Set: Default
Measure-Command [-Expression] <ScriptBlock> [-InputObject <PSObject> ] [ <CommonParameters>]




Detailed Description

The Measure-Command cmdlet runs a script block or cmdlet internally, times the execution of the operation, and returns the execution time.

Parameters

-Expression<ScriptBlock>

Specifies the expression that is being timed. Enclose the expression in braces ({}). The parameter name ("Expression") is optional.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-InputObject<PSObject>

Specifies objects representing the expressions to be measured. Enter a variable that contains the objects or type a command or expression that gets the objects.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

true (ByValue)

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see  about_CommonParameters (http://go.microsoft.com/fwlink/p/?LinkID=113216).

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

  • System.Management.Automation.PSObject

    You can pipe an object to Measure-Command.


Outputs

The output type is the type of the objects that the cmdlet emits.

  • System.TimeSpan

    Measure-Command returns a time span object that represents the result.


Notes

  • For more information, type "Get-Help Measure-Command -detailed". For technical information, type "Get-Help Measure-Command -full".

    When specifying multiple values for a parameter, use commas to separate the values. For example, "<parameter-name> <value1>, <value2>".

Examples

-------------------------- EXAMPLE 1 --------------------------

This command measures the time it takes to run a Get-EventLog command that gets the events in the Windows PowerShell event log.


PS C:\> Measure-Command { Get-EventLog "windows powershell" }

-------------------------- EXAMPLE 2 --------------------------

These commands show the value of using a provider-specific filter in Windows PowerShell commands.


 

The first command measures the time it takes to process a recursive Get-ChildItem command that uses the Path parameter to get only .txt files in the C:\Windows directory and its subdirectories.


PS C:\> Measure-Command {Get-ChildItem –Path C:\Windows\*.txt -Recurse}
                
Days : 0
Hours : 0
Minutes : 0
Seconds : 8
Milliseconds : 618
Ticks : 86182763
TotalDays : 9.9748568287037E-05
TotalHours : 0.00239396563888889
TotalMinutes : 0.143637938333333
TotalSeconds : 8.6182763
TotalMilliseconds : 8618.2763

 

The second command measures the time it takes to process a recursive Get-ChildItem command that uses the provider-specific Filter parameter.


PS C:\> Measure-Command {Get-ChildItem C:\Windows -Filter "*.txt" -Recurse}
                
PS C:\>
Days : 0
Hours : 0
Minutes : 0
Seconds : 1
Milliseconds : 140
Ticks : 11409189
TotalDays : 1.32050798611111E-05
TotalHours : 0.000316921916666667
TotalMinutes : 0.019015315
TotalSeconds : 1.1409189
TotalMilliseconds : 1140.9189

Related topics


Invoke-Command

Trace-Command



Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.