Unrealistically low CPU usage playing back some videos
Posted: 27 Dec 2005 22:09
I, and at least one other person, have a strange behaviour with VLC playing back videos.
My system is a dual Opteron 248 (2.2 ghz), and I'm using Windows XP 32bit SP1, I'm not sure about the other person.
I play back a 640x480 x264 encoded file (in mp4 container), and looking in the Windows Task Manager, my CPU usage barely exceeds 10 percent. After playback of the video (about 4 minutes long), the total CPU time usage recorded for the VLC process is about 13 seconds.
This is unrealistic. That actually means that an old Pentium 1 CPU at perhaps 133 or 166 MHz should be able to play back the video in real time.
If I play the same video in a DirectShow based player, using a heavily compiler-optimized ffdshow for video decoding, I get about 50-75% CPU usage on one of my CPU's (while the other is mainly idle).
Since the VLC results seem unrealistically low, I and several other people I have talked to think VLC is somehow (unintentionally, hopefully ) fooling the Windows process accounting.
Can anyone explain this behaviour?
My system is a dual Opteron 248 (2.2 ghz), and I'm using Windows XP 32bit SP1, I'm not sure about the other person.
I play back a 640x480 x264 encoded file (in mp4 container), and looking in the Windows Task Manager, my CPU usage barely exceeds 10 percent. After playback of the video (about 4 minutes long), the total CPU time usage recorded for the VLC process is about 13 seconds.
This is unrealistic. That actually means that an old Pentium 1 CPU at perhaps 133 or 166 MHz should be able to play back the video in real time.
If I play the same video in a DirectShow based player, using a heavily compiler-optimized ffdshow for video decoding, I get about 50-75% CPU usage on one of my CPU's (while the other is mainly idle).
Since the VLC results seem unrealistically low, I and several other people I have talked to think VLC is somehow (unintentionally, hopefully ) fooling the Windows process accounting.
Can anyone explain this behaviour?