I should have thought about this when we added this column.
without actually collecting CPU samples this would always be NaN. and I don't see much usage for folks to actually need to know the CPU time %.
if it's proven to be something that folks do need we can certainly add it back and actually adjust the keywords for the events we collect to support showing a valid value for it. another reason is this doesn't currently work well on linux (you could use the built in cpu events which would suspend the EE everytime it needs to collect cpu samples so it's not practical to use). for windows the perfview command is this:
Maoni0
commented
2 years ago
I should have thought about this when we added this column.
without actually collecting CPU samples this would always be NaN. and I don't see much usage for folks to actually need to know the CPU time %.
if it's proven to be something that folks do need we can certainly add it back and actually adjust the keywords for the events we collect to support showing a valid value for it. another reason is this doesn't currently work well on linux (you could use the built in cpu events which would suspend the EE everytime it needs to collect cpu samples so it's not practical to use). for windows the perfview command is this:
PerfView /nogui /KernelEvents=Process+Thread+ImageLoad+Profile /ClrEvents=GC+Stack /ClrEventLevel=Informational /BufferSize:3000 /CircularMB:3000 collectwe just need to make the corresponding change when we start the event session.