I have 24 threads. Any tests you want me to do?

[pwnsweet]

Not to brag, but I have access to a machine with 24 threads (2x 6 core Xeon + HT) and was wondering if there were any tests you wanted me to do regarding threading/speed/efficiency.

The CPU's are X5679's. Note that these CPU's DO NOT support AVX instructions. I am using MEGUI and x265 1.0+67.

Let me know if there are any tests you want me to perform and it shall be done.

[zerowalker]

I would personally like to see some x265 tests, let's say a Gaming Capture from a detailed game (Any new game, shooter or whatever) at 1080p (or more), at medium preset.
Just to see how much benefit can be gained at the current state:)

No big research here, just a bit of curiosity.

Do however use x265 through the latest command tool instead of MeGUI, as it's probably quite behind on those builds.

[pwnsweet]

Do however use x265 through the latest command tool instead of MeGUI, as it's probably quite behind on those builds.

Hi. Where can I find a pre-built version of it?

[benwaggoner]

Not to brag, but I have access to a machine with 24 threads (2x 6 core Xeon + HT) and was wondering if there were any tests you wanted me to do regarding threading/speed/efficiency.

The CPU's are X5679's. Note that these CPU's DO NOT support AVX instructions. I am using MEGUI and x265 1.0+67.
I've been testing on 32 thread (16 physical with hyper threading) Ivy Bridge Xeon systems (so AVX but not AVX2). I wonder when we'll actually see a >4 core Haswell Xeon, darn it! This is the longest gap I can recall between an architecture launch for consumers and a full Xeon equivalent.

Anyway...

Doing UHD encode, x265 often hits 100% CPU load using preset veryslow and a no-decode source. But for easier portions of the video, it can drop down to 50% some of the time.

I've been doing my perf testing with a 64-bit x265.exe with y4m and yuv source files reading from a SSD RAID. Using MeGUI, I'd imagine you could easily be bound by AVISynth if it's doing anything even slightly interesting.

There's a good documentation page on threading (http://x265.readthedocs.org/en/default/threading.html) that's worth reading.

[Atak_Snajpera]

In reality for regular 1080p encodes you will have to encode multiple chunks at the same time in order to saturate all logical cores. x265 by default uses CTU 64 (good for quality) which reduces significantly multi-threading potential.