Please share some tips on powershell performance - ctp2

Using the where-object

Measure-command { gwmi win32_logicaldisk | where {$_.drivetype -eq 3} | ft
@{e={([long]$_.freespace/[long]$_.size)*100}}}



Running multiple times, the Total Millisecond on average is about 118-200
total millisecond.



Using the -filter parameter

Measure-command { gwmi win32_logicaldisk -filter "DriveType=3" | ft
@{e={([long]$_.freespace/[long]$_.size)*100}}}



Running multiple times, the Total Millisecond on average is about 69 - 74
total millisecond.



Using .net Class object

Measure-command {[system.io.driveinfo]::getdrives() | where
{$_.drivetype -eq "fixed"} | ft
@{e={([long]$_.totalfreespace/[long]$_.totalsize)*100}}}



Running multiple times, the Total Millisecond on average is about 9 - 10
total millisecond


Any other commands members can share ?

IT STAFF wrote: You just summarized pretty well the prevailing conventional wisdom on
efficiency. As you go lower in (presentation / logic) level, the performance
goes up, generally speaking. And complexity has an inverse relationship to
this.

--
Author, Tech Prosaic blog (http://halr9000.com)
Webmaster, Psi (http://psi-im.org)
Community Director, PowerShellCommunity.org
Co-host, PowerScripting Podcast (http://powerscripting.net)