CCE CPU usage

[flaninacupboard]

Just curious as to other peoples experience on this one. I don't know if it's because of a recent CPU upgrade or just the way CCE works, but while it's running even if i set it's priority to realtime the CPU usage stays on around 75% with 25% just idle. could be my slow RAM (i'm running 256megs of 133 ram in an ATHLON XP2000+) or the fact that the files being encoded are coming over the network (although i doubt it, the usage it still wrong when doing rips on this machine, and the network bandwidth is only at about 20%) or some "feature" of windows XP that makes sure the CPU is never maxed out. any ideas?

[bunyip]

You'll find it's because of the network. Although the bandwidth is not the hold up, it's the delay in the process of communicating and serving the next bit of data between the two machines.

Same thing occurs on mine, if I process a local file the CPU runs at max 100% but if I process a network file it only runs at 73%, it's not getting the data quick enough even though the network is only at 50%.

[SaSi]

I've had exactly the same experience some while ago (and made some posts on this).

I've been having the same utilization (77~80%) on a P4/2.67GHz system with the source AVI on one spindle and the target MPEG-2 on another. Increasing priority didn't make a difference.

I've also noticed in Win2K and WinXP that increasing the priority of a task tends to "deprive" it from resources, something like load balancing attempt from the OS.

However, this is not true for other applications or encoders. Tmpgenc happily strains the CPU as well as Mainconcept.

It seems CCE has a special way of requesting resources that "ensure" that CPU is not utilized to the max. And still is bloody fast, isn't it?

It would be nice to make it 25% faster by achieving a 99% utilization, though.