i7 920 video encoding running at 20 -30%

[manky]

Hi

I don't know if this is the right place to ask but I'm doing a lot of video encoding on my new Titan Onyx and the processor only runs at 20 - 30% when encoding video.

I've tried using VUZE which uses FFMPEG and Handbrake and both get the same results.

SEE HERE

How do I get programs to utilise 100% processing power when encoding or is something else on my system slowing the whole encoding process down?

The only thing I can think is its the HDD which isn't SSD.

Any advice appreciated.

Cheers

manky

 

[Destination]

It like its putting half a thread through each core, ignoring hyperthreading, and being confused about the process so even at that its only send half the information it should to each core.

Try a trial of nerovision, it always used to use each core to max potential when I used it.

You haven't set the program to run at low priority, or to conceed resourses have you?

 

[manky]

Program is running at Normal priority.

Maybe that's how it is supposed to work then as I have just read this which was comparing a Core 2 Quad to an i7...

The i7 was a solid 40% faster. The Core 2 Quad ran at 95% across all 4 Cores while the i7 was around 30% across all cores. The i7 runs at a lower percentage as this chips design has reduced latency on its instruction delivery. It can do more with lower clock speeds than the Core 2.

Still don't understand why it won't go to it's maximum potential speed though.

 

[Temi_D]

The only encoding software I know that is fully multithreaded is Nero vision/recode. Its uses 90% + on all cores when encoding

 

[manky]

Well it must be working properly as I managed to max out the processor when running this test

http://www.techarp.com/showarticle.aspx?artno=520

on the second pass so I guess it's just the way the software works.

x264 HD BENCHMARK 3.0 RESULTS


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Results for x264.exe r1342
--------------------------
encoded 1442 frames, 92.97 fps, 3898.50 kb/s
encoded 1442 frames, 94.17 fps, 3899.02 kb/s
encoded 1442 frames, 93.01 fps, 3899.02 kb/s
encoded 1442 frames, 91.02 fps, 3898.50 kb/s
encoded 1442 frames, 36.73 fps, 3963.07 kb/s
encoded 1442 frames, 37.10 fps, 3956.59 kb/s
encoded 1442 frames, 36.82 fps, 3971.46 kb/s
encoded 1442 frames, 36.73 fps, 3966.62 kb/s


System Details
--------------
Name Intel Core i7 920
product System Product Name
Codename Bloomfield
Specification Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
Specification PC3-12800
Specification PC3-12800
Specification PC3-12800
Core Stepping D0
Technology 45 nm
Stock frequency 2666 MHz
Core Speed 4000.0 MHz

Northbridge Intel X58 rev. 12
Southbridge Intel 82801JR (ICH10R) rev. 00

CAS# latency (CL) 9.0
RAS# to CAS# delay (tRCD) 9
RAS# Precharge (tRP) 9
Cycle Time (tRAS) 28
Command Rate (CR) 2T
Command Rate 2T
Command Rate 2T
Command Rate 2T
Memory Frequency 800.0 MHz (2:8)
Memory Type DDR3
Memory Size 6144 MBytes
Channels Triple

Windows Version Microsoft Windows 7 (6.1) Ultimate Edition (Build 7600)

Number of processors 1
Number of threads 8
Number of threads 8 (max 16)
L2 cache 4 x 256 KBytes, 8-way set associative, 64-byte line size
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T
Package (platform ID) Socket 1366 LGA (0x1)

Temperature 0 45°C (112°F) [0x2D] (SYSTIN)
Temperature 1 55°C (130°F) [0x6D] (CPUTIN)
Temperature 2 3°C (36°F) [0x5] (AUXTIN)
Temperature 0 69°C (156°F) [0x1F] (Core #0)
Temperature 1 66°C (150°F) [0x22] (Core #1)
Temperature 2 61°C (141°F) [0x27] (Core #2)
Temperature 3 62°C (143°F) [0x26] (Core #

 

[Cycrow]

It like its putting half a thread through each core, ignoring hyperthreading, and being confused about the process so even at that its only send half the information it should to each core.

Try a trial of nerovision, it always used to use each core to max potential when I used it.

You haven't set the program to run at low priority, or to conceed resourses have you?

thats normal for a single threaded application.

what windows does is alternate the core that processes each chunk of data
so only 1 core is actually being used at a time.
so instead of getting 100% on one core, it show up more like 50% on each core because its an average load.