Boinc und IvyBridge (OpenCL) Baustelle
- Ersteller Crashtest
- Erstellt am
Im Luxmark rechnet Ivy Bridge mit dem OpenCL 1.2 Treiber schneller als Trinity.
Der BOINC Manager liest die Gflops nur aus, was mehr als fragwürdig erscheint. Egal welcher Treiber oder egal ob ich die GPU mit Furmark 100% belaste, es ändert sich nichts an den 45 gflops. Auf der Basis Freudensprünge zu machen, erscheint seltsam.
orpheus2k
Grand Admiral Special
Ich weiß nicht so recht, was ich aus diesen Daten deuten kann:
EDIT:
Daten hierher verschoben: OpenCL mit iGPU und dGPU
Entschuldige, ich hab dich da einfach falsch verstanden.Meine Rede war nicht von BIOS-Umschaltung, sondern von Umschaltung der Windows-Anzeige (Systemsteuerung > Anpassen > Auflösung anpassen > Diesen Bildschirm als Hauptbildschirm verwenden). Das dauert weniger als 1 Minute und erfordert keinen Neustart.Und ja, selbst bei Ruhezustand-Funktion funktioniert das, so handhabe ich das in 98% meiner Computerstarts.
Manchmal habe ich den Eindruck, Leute wollen nicht verstehen, liegt´s an der Lesekompetenz ? (off topic Ende)
Du scheinst deinen Monitor an beiden Grafikkarten angeschlossen zu haben, um dann wechselst einfach zwischen beiden
Zuletzt bearbeitet:
Crashtest
Redaktion
☆☆☆☆☆☆
Was man daraus sehen kann ? Ganz "einfach" dur hast eine Cayman GPU von AMD mit passenden Treiber installiert und du hast ein Intel CorEI 3770K mit passenden Treiber installiert aber es fehlt die Intel Grafik !!! (inaktiv
)Weiterhin kann ablesen, dass Intel mal wieder um längen hinterher ist - du kannst deine Intel CPU per AMD OpenCL ICD ansprechnen (OpenCL 1.2) oder per Intel OpenCL ICD (nur OpenCL 1.1) und du kannst deine Cayman per OpenCL 1.2 ansprechen
orpheus2k
Grand Admiral Special
Danke für die Info, ich war nicht sicher, ob ein i7 Eintrag nun auch für die HD4000 stehen soll, aber das würde dann wohl extra erwähnt.
Bei GPU-Z kann ich zwischen der HD4000 und der Cayman wählen, wobei wie gesagt bei der Intel der Haken bei OpenCL weiter fehlt (genau wie eine Erwähnung bei AIDA)
Als Resümee zieh ich daraus, dass meine iGPU OpenCL verlernt hat!
Bei GPU-Z kann ich zwischen der HD4000 und der Cayman wählen, wobei wie gesagt bei der Intel der Haken bei OpenCL weiter fehlt (genau wie eine Erwähnung bei AIDA)
Als Resümee zieh ich daraus, dass meine iGPU OpenCL verlernt hat!
clinfo Screnshot an den Entwickler und es ist dann im nächsten GPU-Z drinn, vorausgesetzt darin wird die iGPU von Intel aufgelistet und man gibt ihm Rückmeldng das es funktioniert. GPU-Z sucht nach dem Gerätenamen und wenn es den nicht findet zeigt es an das die GPU kein OpenCl kann. Bei den Llanos hat die GPU unter OpenCl den Namen "BeaverCreek" nach Sumo gesucht und wurde deshalb Anfangs als nicht OpenCl-fähig abgestempelt.
orpheus2k
Grand Admiral Special
In der Vergangenheit hat das ja schon mal funktioniert, da gab es aber auch keine diskrete GPU im System. Seitdem die HD6950 eingebaut ist, will die iGPu kein OpenCL mehr
Für die Entwickler habe ich hier nochmal einen Durchlauf mit OpenCL 1.2 Treiber gemacht.
Number of platforms: 1
Platform Profile: FULL_PROFILE
Platform Version: OpenCL 1.2
Platform Name: Intel(R) OpenCL
Platform Vendor: Intel(R) Corporation
Platform Extensions: cl_intel_dx9_media_sharing cl_khr_byte_addressable_store cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_gl_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics
Platform Name: Intel(R) OpenCL
Number of devices: 2
Device Type: CL_DEVICE_TYPE_CPU
Device ID: 32902
Max compute units: 4
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 1024
Max work group size: 1024
Preferred vector width char: 16
Preferred vector width short: 8
Preferred vector width int: 4
Preferred vector width long: 2
Preferred vector width float: 4
Preferred vector width double: 2
Max clock frequency: 3400Mhz
Address bits: 14757395255531667488
Max memory allocation: 536838144
Image support: Yes
Max number of images read arguments: 480
Max number of images write arguments: 480
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 480
Max size of kernel argument: 3840
Alignment (bits) of base address: 1024
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: Yes
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: No
Round to +ve and infinity: No
IEEE754-2008 fused multiply-add: No
Cache type: Read/Write
Cache line size: 64
Cache size: 262144
Global memory size: 2147352576
Constant buffer size: 131072
Max number of constant args: 480
Local memory type: Global
Local memory size: 32768
Error correction support: 0
Profiling timer resolution: 301
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: Yes
Queue properties:
Out-of-Order: Yes
Profiling : Yes
Platform ID: 00207998
Name: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Vendor: Intel(R) Corporation
Driver version: 1.2
Profile: FULL_PROFILE
Version: OpenCL 1.2 (Build 49972)
Extensions: cl_khr_fp64 cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission cl_intel_exec_by_local_thread cl_khr_gl_sharing cl_intel_dx9_media_sharing cl_khr_dx9_media_sharing cl_khr_d3d11_sharing
Device Type: CL_DEVICE_TYPE_GPU
Device ID: 32902
Max compute units: 16
Max work items dimensions: 3
Max work items[0]: 512
Max work items[1]: 512
Max work items[2]: 512
Max work group size: 512
Preferred vector width char: 1
Preferred vector width short: 1
Preferred vector width int: 1
Preferred vector width long: 1
Preferred vector width float: 1
Preferred vector width double: 0
Max clock frequency: 350Mhz
Address bits: 14757395255531667520
Max memory allocation: 392167424
Image support: Yes
Max number of images read arguments: 128
Max number of images write arguments: 8
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 16
Max size of kernel argument: 1024
Alignment (bits) of base address: 1024
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: No
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: Yes
Round to +ve and infinity: Yes
IEEE754-2008 fused multiply-add: No
Cache type: Read/Write
Cache line size: 64
Cache size: 2097152
Global memory size: 1568669696
Constant buffer size: 65536
Max number of constant args: 8
Local memory type: Scratchpad
Local memory size: 65536
Error correction support: 0
Profiling timer resolution: 80
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue properties:
Out-of-Order: No
Profiling : Yes
Platform ID: 00207998
Name: Intel(R) HD Graphics 4000
Vendor: Intel(R) Corporation
Driver version: 9.17.10.2885
Profile: FULL_PROFILE
Version: OpenCL 1.2
Extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_gl_sharing cl_khr_d3d10_sharing cl_intel_dx9_media_sharing cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_event cl_khr_gl_msaa_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_d3d11_sharing
Platform Profile: FULL_PROFILE
Platform Version: OpenCL 1.2
Platform Name: Intel(R) OpenCL
Platform Vendor: Intel(R) Corporation
Platform Extensions: cl_intel_dx9_media_sharing cl_khr_byte_addressable_store cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_gl_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics
Platform Name: Intel(R) OpenCL
Number of devices: 2
Device Type: CL_DEVICE_TYPE_CPU
Device ID: 32902
Max compute units: 4
Max work items dimensions: 3
Max work items[0]: 1024
Max work items[1]: 1024
Max work items[2]: 1024
Max work group size: 1024
Preferred vector width char: 16
Preferred vector width short: 8
Preferred vector width int: 4
Preferred vector width long: 2
Preferred vector width float: 4
Preferred vector width double: 2
Max clock frequency: 3400Mhz
Address bits: 14757395255531667488
Max memory allocation: 536838144
Image support: Yes
Max number of images read arguments: 480
Max number of images write arguments: 480
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 480
Max size of kernel argument: 3840
Alignment (bits) of base address: 1024
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: Yes
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: No
Round to +ve and infinity: No
IEEE754-2008 fused multiply-add: No
Cache type: Read/Write
Cache line size: 64
Cache size: 262144
Global memory size: 2147352576
Constant buffer size: 131072
Max number of constant args: 480
Local memory type: Global
Local memory size: 32768
Error correction support: 0
Profiling timer resolution: 301
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: Yes
Queue properties:
Out-of-Order: Yes
Profiling : Yes
Platform ID: 00207998
Name: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
Vendor: Intel(R) Corporation
Driver version: 1.2
Profile: FULL_PROFILE
Version: OpenCL 1.2 (Build 49972)
Extensions: cl_khr_fp64 cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission cl_intel_exec_by_local_thread cl_khr_gl_sharing cl_intel_dx9_media_sharing cl_khr_dx9_media_sharing cl_khr_d3d11_sharing
Device Type: CL_DEVICE_TYPE_GPU
Device ID: 32902
Max compute units: 16
Max work items dimensions: 3
Max work items[0]: 512
Max work items[1]: 512
Max work items[2]: 512
Max work group size: 512
Preferred vector width char: 1
Preferred vector width short: 1
Preferred vector width int: 1
Preferred vector width long: 1
Preferred vector width float: 1
Preferred vector width double: 0
Max clock frequency: 350Mhz
Address bits: 14757395255531667520
Max memory allocation: 392167424
Image support: Yes
Max number of images read arguments: 128
Max number of images write arguments: 8
Max image 2D width: 16384
Max image 2D height: 16384
Max image 3D width: 2048
Max image 3D height: 2048
Max image 3D depth: 2048
Max samplers within kernel: 16
Max size of kernel argument: 1024
Alignment (bits) of base address: 1024
Minimum alignment (bytes) for any datatype: 128
Single precision floating point capability
Denorms: No
Quiet NaNs: Yes
Round to nearest even: Yes
Round to zero: Yes
Round to +ve and infinity: Yes
IEEE754-2008 fused multiply-add: No
Cache type: Read/Write
Cache line size: 64
Cache size: 2097152
Global memory size: 1568669696
Constant buffer size: 65536
Max number of constant args: 8
Local memory type: Scratchpad
Local memory size: 65536
Error correction support: 0
Profiling timer resolution: 80
Device endianess: Little
Available: Yes
Compiler available: Yes
Execution capabilities:
Execute OpenCL kernels: Yes
Execute native function: No
Queue properties:
Out-of-Order: No
Profiling : Yes
Platform ID: 00207998
Name: Intel(R) HD Graphics 4000
Vendor: Intel(R) Corporation
Driver version: 9.17.10.2885
Profile: FULL_PROFILE
Version: OpenCL 1.2
Extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_gl_sharing cl_khr_d3d10_sharing cl_intel_dx9_media_sharing cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_event cl_khr_gl_msaa_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_d3d11_sharing
Zuletzt bearbeitet:
orpheus2k
Grand Admiral Special
Ich habe mein Problem mal in einen eigenen Thread (http://www.planet3dnow.de/vbulletin/showthread.php?t=409872) verschoben, ist ja doch eher offtopic
orpheus2k
Grand Admiral Special
Ich habe den neuen Intel Grafiktreiber 9.17.10.2932 (15.28.12) vom 8. Januar 2013 mit der letzten BOINC Version 7.0.44 ausprobiert:
Fall1: Monitor an der Intel GPU ist der Hauptbildschirm
Warum erkennt BOINC die Intel GPU nur, wenn an dieser der Hauptbildschirm angeschlossen ist? Kann dies am Treiber liegen?
Fall1: Monitor an der Intel GPU ist der Hauptbildschirm
Fall2: Monitor an der ATI GPU ist der Hauptbildschirm
Warum erkennt BOINC die Intel GPU nur, wenn an dieser der Hauptbildschirm angeschlossen ist? Kann dies am Treiber liegen?
X1900AIW
Lt. Commander
- Mitglied seit
- 03.02.2009
- Beiträge
- 149
- Renomée
- 10
Was hat es mit der VirtualBox auf sich, in welcher Umgebung läuft dein BOINC ? Die Version 4.2.6 müsste die neueste vom 19.12.2012 sein, vielleicht rührt dein Problem daher. Sobald du eine VM nutzt, könnte deren Initialisierungszeitpunkt eine Rolle spielen. Die externe Grafikkarte hast du gewechselt, sehe ich gerade (6970 auf 7770).
Die "Erkennung" der iGPU ist m.E. einfach noch rudimentär.
Was steht denn aktuell in deinem BIOS unter Init Display First ? Siehe mein Kommentar.
Bei mir keine Neuigkeiten seit 7.0.44, die VRAM-Größe wird falsch ausgegeben:
Die "Erkennung" der iGPU ist m.E. einfach noch rudimentär.
Was steht denn aktuell in deinem BIOS unter Init Display First ? Siehe mein Kommentar.
Bei mir keine Neuigkeiten seit 7.0.44, die VRAM-Größe wird falsch ausgegeben:
Code:
09.01.2013 21:39:47 | | Starting BOINC client version 7.0.44 for windows_x86_64
09.01.2013 21:39:47 | | OpenCL: intel_gpu GPU 0: Intel(R) HD Graphics 4000 (driver version 9.17.10.2867, device version OpenCL 1.1, 1240MB, 1240MB available, 45 GFLOPS peak)orpheus2k
Grand Admiral Special
BOINC läuft nicht in einer VirtualBox, die Zeile "13/01/2013 23:12:09 | | VirtualBox version: 4.2.6" bedeutet nur, dass BOINC eine Installation von VirtualBox erkannt hat, sodass Projekte ihre Apps in der VirtualBox laufen lassen können. Der Support für VirtualBox wurde vor längerem integriert.
Den Value von Init Display First muss ich nachsehen, ich glaube aber AUTO.
Die Angabe des VRAM ist bei mir auch falsch, sollten 1024 MB sein.
Den Value von Init Display First muss ich nachsehen, ich glaube aber AUTO.
Die Angabe des VRAM ist bei mir auch falsch, sollten 1024 MB sein.
orpheus2k
Grand Admiral Special
@ X1900AIW
Ich war dir noch ne Antwort schuldig, Init Display First steht auf Auto.
Ich habe sowohl iGPU als auch PEG probiert, in beiden Fällen erkennt BOINC die HD4000 nicht als OpenCL Device
Ich war dir noch ne Antwort schuldig, Init Display First steht auf Auto.
Ich habe sowohl iGPU als auch PEG probiert, in beiden Fällen erkennt BOINC die HD4000 nicht als OpenCL Device
X1900AIW
Lt. Commander
- Mitglied seit
- 03.02.2009
- Beiträge
- 149
- Renomée
- 10
Was steht bei dir unter:
Internal Display: AUTO ?
Siehe #70 bzw. #71.
Nochmal: falls du bootest von iGPU (Monitorkabel dran, Kabel an externer Grafikkarte weg), wird AUTO eine andere Auswirkung haben als bei ENABLED (Dauerfunktion = ständig verfügbar, unbhängig von externer Grafikkarte).
Mehr kann ich nicht helfen, als den Rat systematisch vorzugehen und logische Abfolgen zu prüfen. Bei mir funktioniert es, LUCID verwende ich nicht. Falls LUCID bei dir ohnehin nicht läuft, mache doch mal den Versuch und deinstalliere es, boote neu und nächster Versuch. Ich für meinen Teil brauche keine GPU-Tools, die BOINC potentiell behindern. Derzeit ist die iGPU-Unterstützung noch offen, sobald aber Workunits da sind, soll die Kiste rechnen können.
Internal Display: AUTO ?
Siehe #70 bzw. #71.
Nochmal: falls du bootest von iGPU (Monitorkabel dran, Kabel an externer Grafikkarte weg), wird AUTO eine andere Auswirkung haben als bei ENABLED (Dauerfunktion = ständig verfügbar, unbhängig von externer Grafikkarte).
Mehr kann ich nicht helfen, als den Rat systematisch vorzugehen und logische Abfolgen zu prüfen. Bei mir funktioniert es, LUCID verwende ich nicht. Falls LUCID bei dir ohnehin nicht läuft, mache doch mal den Versuch und deinstalliere es, boote neu und nächster Versuch.
Ich für meinen Teil brauche keine GPU-Tools, die BOINC potentiell behindern. Derzeit ist die iGPU-Unterstützung noch offen, sobald aber Workunits da sind, soll die Kiste rechnen können.orpheus2k
Grand Admiral Special
Schon klar, die Intel HD4000 werden von den Projekten noch nicht unterstützt. Ich will mich nur drauf vorbereiten und bin dann doch etwas verdutzt, welche Ergebnisse dabei rauskommen!
Internal Display ist übrigens 'Enabled'
Internal Display ist übrigens 'Enabled'
Fränki´s Welle
Grand Admiral Special
Bei Seti tut sich was!!!!!!
Optimierte App von Raistmer: (Steht am Ende des Text)
Optimierte App von Raistmer: (Steht am Ende des Text)
AstroPulse OpenCL application currently available in 3 editions: for AMD/ATi, nVidia and Intel GPUs.
It's intended to process SETI@home AstroPulse v6 tasks.
Build revision:1764
Date of revision commit: 2013/02/02 15:47:49
Available command line switches:
-v N :sets level of verbosity of app. N - integer number.
-ffa_block N :sets how many FFA's different period iterations will be processed per kernel call. N should be integer even number less than 32768.
-ffa_block_fetch N: sets how many FFA's different period iterations will be processed per "fetch" kernel call (longest kernel in FFA).
N should be positive integer number, should be divisor of ffa_block_N.
-unroll N :sets number of data chunks processed per kernel call in main application loop. N should be integer number, minimal possible value is 2.
-skip_ffa_precompute : Results in skipping FFA pre-compute kernel call. Affects performance. Experimentation required if it will increase or decrease performance on particular GPU/CPU combo.
-exit_check :Results in more often check for exit requests from BOINC. If you experience problems with long app suspend/exit use this option.
Can decrease performance though.
-use_sleep :Results in additional Sleep() calls to yield CPU to other processes. Can affect performance. Experimentation required.
-initial_ffa_sleep N M: In PC-FFA will sleep N ms for short and M ms for large one before looking for results. Can decrease CPU usage.
Affects performance. Experimentation required for particular CPU/GPU/GPU driver combo. N and M should be integer non-negative numbers.
Approximation of useful values can be received via running app with -v 2 and -use_sleep switches enabled and analyzing stderr.txt log file.
-sbs N :Sets maximum single buffer size for GPU memory allocations. N should be positive integer and means bigger size in Mbytes.
For now if other options require bigger buffer than this option allows warning will be issued but memory allocation attempt will be made.
-hp : Results in bigger priority for application process (normal priority class and above normal thread priority).
Can be used to increase GPU load, experimentation required for particular GPU/CPU/GPU driver combo.
-cpu_lock :Results in CPUs number limitation for particular app instance. Also attempt to bind different instances to different CPU cores will be made.
Can be used to increase performance under some specific conditions. Can decrease performance in other cases though. Experimentation required.
Here some already obsolete options are listed. They are not tested for proper operation with latest builds and are only listed for completeness:
-gpu_lock :Old way GPU lock enabled. Use -instances_per_device N switch to provide number of instances to run.
-instances_per_device N :Sets allowed number of simultaneously executed GPU app instances (shared with MultiBeam app instances).
N - integer number of allowed instances.
-disable_slot N: Can be used to exclude N-th GPU (starting from zero) from usage.
Not tested and obsolete feature, use BOINC abilities to exclude GPUs instead.
These 2 options used together provide BOINC-independent way to limit number of simultaneously
executing GPU apps. Each SETI OpenCL GPU application with these switches enabled will create/check global Mutexes and suspend its process
execution if limit is reached. Awaiting process will consume zero CPU/GPU and rather low amount of memory awaiting when it can continue execution.
These switches can be placed into the file called ap_cmdline.txt also.
Examples of app_info.xml entries (don't forget to replace listed executable name with real executable name and place <app_info> and </app_info>
tags at the beginning and the end of file correspondingly):
for ATi GPU:
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1764.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_100</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_100</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
For NV GPU:
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_NV_r1764.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_100</plan_class>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_100</plan_class>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
For Intel GPU (currently in beta stage):
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_Intel_r1764.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_intel_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>intel_gpu</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_Intel_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
Known issues:
- With 12.x Catalyst drivers GPU usage can be low if CPU fully used with another loads.
Same applies to NV drivers past 267.xx and to Intel SDK drivers.
If you see low GPU usage of zero blanked tasks try to free one or more CPU cores.
- For overflowed tasks found signal sequence not always match CPU version.
Best usage tips:
For best performance it is important to free 2 CPU cores running multiple instances.
Freeing at least 1 CPU core is necessity to get enough GPU usage.
command line parameters.
_______________________
High end cards (more than 12 compute units)
-unroll 12 -ffa_block 8192 -ffa_block_fetch 4096 -hp
Mid range cards (less than 12 compute units)
-unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -hp
entry level GPU (less than 6 compute units)
-unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -hp
Your mileage might vary.
-----------------------------------------------------
App instances.
______________
On high end cards HD 5850/5870, 6950/6970, 7950/7970 you can run 3 instances.
On mid range cards HD 5770, 6850/6870, 7850/7870 best performance should be running 2 instances.
If you experience screen lags reduce unroll factor and ffa_block_fetch value.
Addendum:
_________
Running multiple cards in a system requires freeing another CPU core.
It's intended to process SETI@home AstroPulse v6 tasks.
Build revision:1764
Date of revision commit: 2013/02/02 15:47:49
Available command line switches:
-v N :sets level of verbosity of app. N - integer number.
-ffa_block N :sets how many FFA's different period iterations will be processed per kernel call. N should be integer even number less than 32768.
-ffa_block_fetch N: sets how many FFA's different period iterations will be processed per "fetch" kernel call (longest kernel in FFA).
N should be positive integer number, should be divisor of ffa_block_N.
-unroll N :sets number of data chunks processed per kernel call in main application loop. N should be integer number, minimal possible value is 2.
-skip_ffa_precompute : Results in skipping FFA pre-compute kernel call. Affects performance. Experimentation required if it will increase or decrease performance on particular GPU/CPU combo.
-exit_check :Results in more often check for exit requests from BOINC. If you experience problems with long app suspend/exit use this option.
Can decrease performance though.
-use_sleep :Results in additional Sleep() calls to yield CPU to other processes. Can affect performance. Experimentation required.
-initial_ffa_sleep N M: In PC-FFA will sleep N ms for short and M ms for large one before looking for results. Can decrease CPU usage.
Affects performance. Experimentation required for particular CPU/GPU/GPU driver combo. N and M should be integer non-negative numbers.
Approximation of useful values can be received via running app with -v 2 and -use_sleep switches enabled and analyzing stderr.txt log file.
-sbs N :Sets maximum single buffer size for GPU memory allocations. N should be positive integer and means bigger size in Mbytes.
For now if other options require bigger buffer than this option allows warning will be issued but memory allocation attempt will be made.
-hp : Results in bigger priority for application process (normal priority class and above normal thread priority).
Can be used to increase GPU load, experimentation required for particular GPU/CPU/GPU driver combo.
-cpu_lock :Results in CPUs number limitation for particular app instance. Also attempt to bind different instances to different CPU cores will be made.
Can be used to increase performance under some specific conditions. Can decrease performance in other cases though. Experimentation required.
Here some already obsolete options are listed. They are not tested for proper operation with latest builds and are only listed for completeness:
-gpu_lock :Old way GPU lock enabled. Use -instances_per_device N switch to provide number of instances to run.
-instances_per_device N :Sets allowed number of simultaneously executed GPU app instances (shared with MultiBeam app instances).
N - integer number of allowed instances.
-disable_slot N: Can be used to exclude N-th GPU (starting from zero) from usage.
Not tested and obsolete feature, use BOINC abilities to exclude GPUs instead.
These 2 options used together provide BOINC-independent way to limit number of simultaneously
executing GPU apps. Each SETI OpenCL GPU application with these switches enabled will create/check global Mutexes and suspend its process
execution if limit is reached. Awaiting process will consume zero CPU/GPU and rather low amount of memory awaiting when it can continue execution.
These switches can be placed into the file called ap_cmdline.txt also.
Examples of app_info.xml entries (don't forget to replace listed executable name with real executable name and place <app_info> and </app_info>
tags at the beginning and the end of file correspondingly):
for ATi GPU:
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1764.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>ati_opencl_100</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_ati_100</plan_class>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
For NV GPU:
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_NV_r1764.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_100</plan_class>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_100</plan_class>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
For Intel GPU (currently in beta stage):
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_Intel_r1764.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_intel_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>intel_gpu</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_Intel_r1764.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
Known issues:
- With 12.x Catalyst drivers GPU usage can be low if CPU fully used with another loads.
Same applies to NV drivers past 267.xx and to Intel SDK drivers.
If you see low GPU usage of zero blanked tasks try to free one or more CPU cores.
- For overflowed tasks found signal sequence not always match CPU version.
Best usage tips:
For best performance it is important to free 2 CPU cores running multiple instances.
Freeing at least 1 CPU core is necessity to get enough GPU usage.
command line parameters.
_______________________
High end cards (more than 12 compute units)
-unroll 12 -ffa_block 8192 -ffa_block_fetch 4096 -hp
Mid range cards (less than 12 compute units)
-unroll 10 -ffa_block 6144 -ffa_block_fetch 1536 -hp
entry level GPU (less than 6 compute units)
-unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -hp
Your mileage might vary.
-----------------------------------------------------
App instances.
______________
On high end cards HD 5850/5870, 6950/6970, 7950/7970 you can run 3 instances.
On mid range cards HD 5770, 6850/6870, 7850/7870 best performance should be running 2 instances.
If you experience screen lags reduce unroll factor and ffa_block_fetch value.
Addendum:
_________
Running multiple cards in a system requires freeing another CPU core.
wintermute_3dc
Admiral Special
[STRIKE]
Kannst du bitte noch den Link posten wo du das gefunden hast?[/STRIKE]
Ich würde es vielleicht mal versuchen.
Edit: Danke @X1900AIW für den Link
Edit2: Nur Programme für Windows
Zuletzt bearbeitet:
Es gibt übrigens einen offiziellen Folding @Home Benchmark: http://fahbench.com/
X1900AIW
Lt. Commander
- Mitglied seit
- 03.02.2009
- Beiträge
- 149
- Renomée
- 10
Hat das was mit diesem Thread zu tun ?
Ähnliche Themen
