Message boards : Development : Doublevector always uses SSE path instead of AVX
Good day Today,
It seems that haswell in 2017 was not very performant with AVX at the time and therefor it was disabled.
Running the compiled verion as follows:
bin/pc input/tile2.txt output/output2.txt 0.05 1 100000 0
The avx realtime is 22 second, the SSE version realtime is 32 seconds under ubuntu in hyper-v.
This only helps if the 5th parameter (100000) is large enough. If it is small like the test_run.sh scripts it almost makes no difference.
Could someone verify that the compiled gene_pcim_v1.11_win64__avx.exe is running in SSE instead of AVX mode?
|ID: 2105 · Reply Quote|
The Windows source code is exactly the same of the Linux one, it was compiled using gcc/MinGW so I guess the behavior is the same.
|ID: 2108 · Reply Quote|
I'm looking into it and see that it is running several sets. Each set runs for about 13 seconds. After that a new set begins.
|ID: 2115 · Reply Quote|
Message boards :
Doublevector always uses SSE path instead of AVX