x264's CPU usage dropping..

MoUCLAs · 2nd October 2007, 06:32

When i make a compressibility test suddenly the cpu usage is dropping in some .ts files that i try to rencode. It happens days before and i downloaded the latest (680) and it made the compressibility test just fine, but today it happend again.. What's wrong?

Ranguvar · 2nd October 2007, 20:08

Not sure what you mean.

As in, the CPU usage decreases over time as encoding? That's normal, it will fluctuate. Or the second time you encode the TS, the CPU usage is lower? Perhaps it has already cached some of the TS and that is why.

Sagekilla · 2nd October 2007, 20:11

If CPU usage fluctuates, that's completely normal as Ranguvar said. But, if you mean that suddenly CPU usage will drop by a large amount and STAY there, that's abnormal. And the fact that you've encountered this on a newer revision, it sounds like the ts files (since you did say that it occurs only on some) you're encoding may be at fault.

2nd October 2007, 06:32	#1 \| Link
MoUCLAs Encoding for people.. Join Date: Apr 2004 Posts: 35	x264's CPU usage dropping.. When i make a compressibility test suddenly the cpu usage is dropping in some .ts files that i try to rencode. It happens days before and i downloaded the latest (680) and it made the compressibility test just fine, but today it happend again.. What's wrong? __________________ We Capture.. you Watch..

2nd October 2007, 20:08	#2 \| Link
Ranguvar Registered User Join Date: Feb 2007 Location: ::1 Posts: 1,236	Not sure what you mean. As in, the CPU usage decreases over time as encoding? That's normal, it will fluctuate. Or the second time you encode the TS, the CPU usage is lower? Perhaps it has already cached some of the TS and that is why.

2nd October 2007, 20:11	#3 \| Link
Sagekilla x264aholic Join Date: Jul 2007 Location: New York Posts: 1,752	If CPU usage fluctuates, that's completely normal as Ranguvar said. But, if you mean that suddenly CPU usage will drop by a large amount and STAY there, that's abnormal. And the fact that you've encountered this on a newer revision, it sounds like the ts files (since you did say that it occurs only on some) you're encoding may be at fault.