Log in

View Full Version : Ridiculously low CPU usage when encoding XviD on Quad Core

duckdown
17th December 2007, 05:19
Hi all..

Am having an incredibly annoying problem..

I have a 3.0ghz Quad Core Xeon I am using for encoding, yet, my CPU usage never gets above 35% ! I press ALT+CTRL+DEL and look a the PERFORMANCE tab and it looks like only the last 2 cores are even being utilized!

This is making for incredibly time-consuming encodes and I do not know what to do to fix it

Can somebody please help me.. I am using VirtualDubMod to encode.

My xvid is being reported as version 1.1.2.

My .avs looks like this (basically just a template in my GUI frontend):

MPEG2Source("C:\tmp\myfile.d2v")
Crop(6,2,-10,-2)
FieldDeinterlace(blend=false)
Lanczos4Resize(512,384)
FluxSmoothT(2)

Help would be GREATLY appreciated because the performance is pretty appalling. Is there some way to specify more threads or something?

Thanks in advance!! Will be constantly checking for a reply.

Cheers
Dark Shikari
17th December 2007, 05:33
That's because Xvid is singlethreaded...
squid_80
17th December 2007, 06:49
Even if you were using a multithreaded version (1.2 onwards), don't expect to see super fast encodes with 100% cpu usage. The most you'll probably see is about 60% on a quad, considerably less when you're using a resolution of 512x384.

(Also, "incredibly time-consuming"? Bit of an exaggeration, don't you think? I can't imagine that script being any slower than realtime.)
LoRd_MuldeR
17th December 2007, 13:25
duckdown, in case H.264 is acceptable as output format for your purpose (instead of MPEG-4 ASP), you may consider switching to x264.
It's always nice to see x264 using all four cores at 100% load :)
burfadel
17th December 2007, 14:25
duckdown, in case H.264 is acceptable as output format for your purpose (instead of MPEG-4 ASP), you may consider switching to x264.
It's always nice to see x264 using all four cores at 100% load :)

Not to mention more efficient encoding bitrate wise with the correct settings!
Inventive Software
19th December 2007, 17:26
AviSynth is the bottleneck. Use MT to specify 4 threads, and see if that helps. Search for more, cause it's not the first time AviSynth's been the issue. ;)