FLAC x64 build, 64 bit build of flac.exe Options

[viktor]

I saw a benchmark on Phoronix regarding FLAC performance:



So I became curious about it on Windows. The results? A bit disappointing, only about 3-5% increase in performance, probably because of the lack of _asm on x64. If the x86 build is compiled without using NASM, it gets about 10% slower. At least on my AMD Fusion A6-3500. Either way, here it is for your convenience!

Download:

1. Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)
2. FLAC 1.2.1 x64

This post has been edited by viktor: Nov 4 2011, 22:22

[forart.eu]

Dunno if this can help, but i recently had a talk with Eric Gur (Processor Client Application Engineer @ Intel Corp.) about MT libraries, here's his answer:

For threading I recommend using Intel's free TBB library. It's very fast, cross platform, simple to use and has an important feature - malloc replacement.
I used it in a previous project - 1M lines of code, multithreaded application on Linux x64. Just the malloc replament boosted performance by 3x without changing any code (1 line in the makefile).

Dunno if can help, but could be really interesting !

Using a 2500k @ 4.2 ghz

OT: Same here, what about 4.2 oc settings ?

This post has been edited by db1989: Dec 27 2011, 14:43

Reason for edit: merging posts; please edit instead

[Martel]

For threading I recommend using Intel's free TBB library. It's very fast, cross platform, simple to use and has an important feature - malloc replacement.
I used it in a previous project - 1M lines of code, multithreaded application on Linux x64. Just the malloc replament boosted performance by 3x without changing any code (1 line in the makefile).

Malloc replacement in a multi-threaded application is only going to help in case all the threads are doing mallocs/frees repeatedly/in parallel (the normal heap is a serialization/choke point). I'm not sure why an encoder would need to do that when it could have most of the buffers "static" (malloc'd upon startup, freed upon exit).

It's great for server code with lots of messaging and modeled dynamic data types.