Message boards :
Number crunching :
GPU Detection ?
Message board moderation
Author | Message |
---|---|
Send message Joined: 22 Jan 09 Posts: 35 Credit: 46,731,190 RAC: 0 |
Below is the output file from a sample WU from one of my hosts .... stderr out <core_client_version>6.10.43</core_client_version> <![CDATA[ <stderr_txt> Running Milkyway@home ATI GPU application version 0.23 (Win64, CAL 1.4) by Gipsel ignoring unknown input argument in app_info.xml: -np ignoring unknown input argument in app_info.xml: 20 ignoring unknown input argument in app_info.xml: -p ignoring unknown input argument in app_info.xml: 0.8141631010093290000000000 ignoring unknown input argument in app_info.xml: 5.1474444927700760000000000 ignoring unknown input argument in app_info.xml: -1.2815947200320840000000000 ignoring unknown input argument in app_info.xml: 171.7776143626600700000000000 ignoring unknown input argument in app_info.xml: 22.2262864212139700000000000 ignoring unknown input argument in app_info.xml: 3.3868236645853070000000000 ignoring unknown input argument in app_info.xml: 0.0000562598815600000000000 ignoring unknown input argument in app_info.xml: 4.0206936216241020000000000 ignoring unknown input argument in app_info.xml: -4.7971545700480620000000000 ignoring unknown input argument in app_info.xml: 168.8427062952647800000000000 ignoring unknown input argument in app_info.xml: 0.7077170036007965000000000 ignoring unknown input argument in app_info.xml: 5.0683153488622010000000000 ignoring unknown input argument in app_info.xml: 1.7988182168921810000000000 ignoring unknown input argument in app_info.xml: 1.0000000000000000000000000 ignoring unknown input argument in app_info.xml: -1.7505235684361340000000000 ignoring unknown input argument in app_info.xml: 151.7041348085007300000000000 ignoring unknown input argument in app_info.xml: 11.7211628475786970000000000 ignoring unknown input argument in app_info.xml: 3.6732927762312090000000000 ignoring unknown input argument in app_info.xml: 5.3702346912884495000000000 ignoring unknown input argument in app_info.xml: 19.6417083200254550000000000 instructed by BOINC client to use device 0 CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (4 cores/threads) 3.4 GHz (292ms) CAL Runtime: 1.4.515 Found 2 CAL devices Device 0: ATI Radeon HD4700/4800 (RV740/RV770) 1024 MB local RAM (remote 64 MB cached + 2048 MB uncached) GPU core clock: 900 MHz, memory clock: 490 MHz 800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads supporting double precision Device 1: ATI Radeon HD4700/4800 (RV740/RV770) 1024 MB local RAM (remote 64 MB cached + 2048 MB uncached) GPU core clock: 900 MHz, memory clock: 490 MHz 800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads supporting double precision Starting WU on GPU 0 main integral, 640 iterations (1600x1400), 3 streams predicted runtime per iteration is 233 ms (33.3333 ms are allowed), dividing each iteration in 7 parts borders of the domains at 0 232 464 688 920 1144 1376 1600 Calculated about 3.28897e+013 floatingpoint ops on GPU, 2.47165e+008 on FPU. Approximate GPU time 149.5 seconds. probability calculation (100788 stars) Calculated about 3.34818e+009 floatingpoint ops on FPU. WU completed. CPU time: 1.46875 seconds, GPU time: 149.5 seconds, wall clock time: 150.944 seconds, CPU frequency: 3.4 GHz </stderr_txt> ]]> Question 1) Are the descriptions of my two GPUs (in bold) provided by the MilkyWay app, or does this information come from the BOINC client.? Reason for asking is that the information is wrong. Both GPUs are described identically including core clock timings, yet one GPU runs at the stated 900MHz, but the other one runs at 950MHz (confirmed by both GPU-Z and Catalyst Control Center). Question 2) Because they are described identically (even when they are not), can I tell which is which? Is device0=GPU1 in CCC and device1=GPU2 in CCC ??? Or might they be reported differently at different times? |
Send message Joined: 22 Jan 09 Posts: 35 Credit: 46,731,190 RAC: 0 |
bump |
©2024 Astroinformatics Group