- Aug 11, 2016
- 1,679
- 715
- 136
Last night I was doing Milkyway@Home benchmark and this afternoon finally got time to compare it with others. While doing it, I've found an interesting finding. Here's my partial stderr output.
CPU: AMD Athlon x4 845 (excavator uarch)
And for comparison, I use iwajabitw's partial stderr output (apologise for unauthorised access on your database).
CPU: AMD FX-6300 (piledriver uarch)
My question is, why did even though both client basically use same CPU arch (bulldozer derivative) but milkyway app decide to use different instruction set? Can it be manually selected?
Code:
<core_client_version>7.8.2</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 5 </number_WUs>
<number_params_per_WU> 20 </number_params_per_WU>
Using AVX path
And for comparison, I use iwajabitw's partial stderr output (apologise for unauthorised access on your database).
Code:
<core_client_version>7.8.3</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 5 </number_WUs>
<number_params_per_WU> 20 </number_params_per_WU>
Using SSE4.1 path
My question is, why did even though both client basically use same CPU arch (bulldozer derivative) but milkyway app decide to use different instruction set? Can it be manually selected?