Get CPU for process in powershell

Ok, just realized what was happening. The dafault "Memory" column in Task Manager is actually representing the Private Working Set, not Working Set from Powershell, that represents private and shared memory with other process. Just enabled the "Memory - Working Set" column in Task Manager and it matches.

Obviously the values in Powershell are in bytes, need to calculate to Mb.

This page was also helpful:

http://windows.microsoft.com/en-us/windows/what-task-manager-memory-columns-mean#1TC=windows-7

With object properties "Name" is a read-only property, and so cannot be changed during runtime.

$objTest = New-Object -TypeName PSObject -Property @{ Foo = 42; Bar = 99 }
$objTest.PSObject.Properties["Foo"].Name  # Output: Foo.
$objTest.PSObject.Properties["Foo"].Name = "NotFoo"  # Output: 'Name' is a ReadOnly property.

An alternate to creating a new property and copying values may be to create a new "AliasProperty", which is a new property (with its own name) that is simply linked to an existing property.

eg.:

PS Y:\> $objTest | Add-Member -MemberType AliasProperty -Name Notfoo -Value Foo
PS Y:\> $objtest

Bar Foo Notfoo
--- --- ------
 99  42     42

PS Y:\> $objtest.Foo = 123
PS Y:\> $objtest

Bar Foo Notfoo
--- --- ------
 99 123    123