Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: HCC GPU Beta July 12 |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 47
|
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As long as it has it you should be fine. Don't have an ATI card yet but I saw that statement floating around Einstein. As long as people have the opencl driver than they're good.
|
||
|
Bearcat
Master Cruncher USA Joined: Jan 6, 2007 Post Count: 2803 Status: Offline Project Badges: |
Received 16. 15 valid, 1 pending validation. Less than 3 hrs to get me gold badge. Bummer!
----------------------------------------
Crunching for humanity since 2007!
----------------------------------------[Edit 1 times, last edit by Bearcat at Jul 13, 2012 3:35:30 AM] |
||
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges: |
In the past ATI shipped OpenCL libraries with the SDK but they have been moved to the drivers some time ago.
Thanks, armstrdj |
||
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: |
In the past ATI shipped OpenCL libraries with the SDK but they have been moved to the drivers some time ago. The 12.4 driver works for me, but the later ones (e.g., 12.6) do not.Thanks, armstrdj However, I upgraded from 12.4 to 12.7 beta and it still works, though it seems to have just kept the same version of OpenCL that was included in 12.4. |
||
|
XSmeagolX
Senior Cruncher Joined: Nov 12, 2009 Post Count: 444 Status: Offline Project Badges: |
I had one WU, that takes more than 10h on my i7 with AMD/ATI Radeon HD 5800 using CCC 12-4 on Win7/64bit...
----------------------------------------I checked this morning and this WU was still running.... I paused it, crunched the other 3 Betas on this machine and restart this Workunit again... Now it has finished and is on pending validation at the moment... Result Name: BETA_ X0000038271227200409250008_ 1-- Info of the Boinctasks-Log: ------------------------------- 1904 World Community Grid 12.07.2012 21:48:22 Started download of BETA_X0000038271227200409250008_X0000038271227200409250008.jp2 1905 World Community Grid 12.07.2012 21:48:22 Started download of cfsw_8117_08117800_B08117800.sql 1906 World Community Grid 12.07.2012 21:48:24 Finished download of BETA_X0000038271227200409250008_X0000038271227200409250008.jp2 1972 World Community Grid 12.07.2012 21:59:14 Starting task BETA_X0000038271227200409250008_1 using beta3 version 647 Part of the file: ----------------- . . . Total time for ../../projects/www.worldcommunitygrid.org/BETA_X0000038271227200409250008_X0000038271227200409250008.jp2: 773 seconds Finished Image #0, pctComplete = 1.000000 CPU time used = 104.817072 09:13:14 (5952): called boinc_finish
WCG-Team Captain of Team SETI.Germany
----------------------------------------(official Partner of World Community Grid) [Edit 2 times, last edit by XSmeagolX at Jul 13, 2012 7:49:09 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Looks like not many people had the CPU overcaching problems i told about in the beginning of the thread. So i think it's something buggy in the client version 6.10.60. To sum it up: While the 1.00ATI+1.00CPU HCC Betas were running, Boinc kept one of 8 threads free (client set to 100% of CPUs). Whenever the estimated GPU cache went below my cache setting (0.15 days), it requested tasks for CPU+GPU, resulting in downloading a non-Beta CPU task, ignoring how big the CPU cache was already. The GPU handling only 1 task at a time can only cache up to 4 Betas, so setting the cache higher than the 4 tasks Beta cache, the client would be downloading CPU tasks endlessly. 8 GPU tasks went fine, 3 were failing (at the same second somehow). As i said before, a previously running GPU task was resumed (had been auto-suspended for a repair GPU task), and after some time it errored out and took the other 2 tasks cached up with it to errorland. Maybe an unfinished GPU task is doing something wrong to the video memory? Just a thought. Well, i keep on crunching the big CPU pile for now. I also ran into to the over cache problem. Running a 0.2 day cache the 5 machines that ran Beta's ended up with a 1.6 to 9.1 day cache before I got them stopped. BOINC was requesting and receiving new CPU tasks (as you describe) and at the same time was stopping and starting High Priority CPU tasks. All in all quite a mess that's going to take a while to return to normal. BOINC client+mgr: 6.10.58 OS: Win 7 (64) and XP (32) GPU: (1) ATI and (4) NVidia Just when i wrote the above comment, i received a single repair GPU Beta wu, so the GPU cache was definitely lower than my 0.15 days setting, whilst my CPU cache had been grown to several days - but the problem did not occur any more (it just requested for GPU tasks as it should). Very strange. I have no idea why it had been requesting for CPUs non-stop before. Like the jobs before, Boinc suspended one of 8 CPU threads. There is another comment very similar to that in the CFSW problems thread https://secure.worldcommunitygrid.org/forums/...33000_lastpage,yes#384756 . My client has been also been running exclusively CFSW work units apart from the Betas (6.11 and 6.12 to be exact). Hmmm... edit: correct link [Edit 1 times, last edit by Former Member at Jul 13, 2012 8:50:45 AM] |
||
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4842 Status: Offline Project Badges: |
I was not around to see this happen, but I now have ~17 days of WUs on my only cruncher that received Betas yesterday. Cache was set at 1.0 days. They all downloaded between 18:00 and 19:11 even though I received Betas (22 in all) between 17:06 and 23:11 so it was intermittent. I'll abort most of them today. 6.10.58.
---------------------------------------- |
||
|
sgoll
Advanced Cruncher Joined: Oct 24, 2006 Post Count: 87 Status: Offline Project Badges: |
Well, from a quick look I would say, the problem with the cache is caused by the "stone age" old boinc version you are running. wplachy is running 6.10.58, deltavee too, herna runs 6.10.60. When I look at http://boinc.berkeley.edu/trac/wiki/VersionHistory then the boinc devs fixed many problems in the newer versions. You should really think about changing to the 6.12 series of boinc software, 6.12.34 seems to be the most recommended version. 7.0.x is ... well ... you may try.
----------------------------------------Stephan [Edit 2 times, last edit by sgoll at Jul 13, 2012 11:00:47 AM] |
||
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4842 Status: Offline Project Badges: |
Well, from a quick look I would say, the problem with the cache is caused by the "stone age" old boinc version you are running. wplachy is running 6.10.58, deltavee too, herna runs 6.10.60. Well, 6.10.58 is the current version recommended by WCG. Hey Techs, what do you think? |
||
|
smeyer55
Senior Cruncher Joined: Feb 15, 2009 Post Count: 303 Status: Offline Project Badges: |
I got 13 beta units with the following results. I'm also doing bitcoin mining with this gpu.
3 Valid, but all 3 had someone else erroring out with the "gpu_type not found" error 1 Errored out with this message <core_client_version>6.10.18</core_client_version> <![CDATA[ <message> - exit code 293 (0x125) </message> <stderr_txt> Commandline: projects/www.worldcommunitygrid.org/wcg_beta3_img_6.47_windows_intelx86__ati14_hcc1 X0000038270550200409250020.jp2 --device 0 INFO: gpu_type not found in init_data.xml. INFO: GPU device not specified in init_data.xml. Checking Commandline. Boinc requested ATI gpu device number0 Found compute platform Advanced Micro Devices, Inc. Selecting this platform CL_DEVICE_NAME: Cayman CL_DEVICE_VENDOR: Advanced Micro Devices, Inc. CL_DEVICE_VERSION: CAL 1.4.1664 (VM) CL_DEVICE_MAX_COMPUTE_UNITS: CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3 CL_DEVICE_MAX_WORK_ITEM_SIZES: 256 / 256 / 256 CL_DEVICE_MAX_WORK_GROUP_SIZE: 256 CL_DEVICE_MAX_CLOCK_FREQUENCY: 870 MHz CL_DEVICE_ADDRESS_BITS: 32 CL_DEVICE_MAX_MEM_ALLOC_SIZE: 200 MByte CL_DEVICE_GLOBAL_MEM_SIZE: 800 MByte CL_DEVICE_ERROR_CORRECTION_SUPPORT: no CL_DEVICE_LOCAL_MEM_TYPE: local CL_DEVICE_LOCAL_MEM_SIZE: 32 KByte CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64 KByte CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE CL_DEVICE_EXTENSIONS: cl_amd_fp64 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_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt cl_khr_d3d10_sharing Estimated kernel execution time = 0.79733 [sec] Starting analysis of ../../projects/www.worldcommunitygrid.org/BETA_X0000038270550200409250020_X0000038270550200409250020.jp2... Extracting GLCM features... 16:05:20 (3704): called boinc_finish Commandline: projects/www.worldcommunitygrid.org/wcg_beta3_img_6.47_windows_intelx86__ati14_hcc1 X0000038270550200409250020.jp2 INFO: gpu_type not found in init_data.xml. INFO: GPU device not specified in init_data.xml. Checking Commandline. ERROR: GPU device not specified in init_data.xml or on command line. Exiting. 16:14:49 (1008): called boinc_finish </stderr_txt> ]]> ========================================= 8 errored out with this message <core_client_version>6.10.18</core_client_version> <![CDATA[ <message> - exit code 293 (0x125) </message> <stderr_txt> Commandline: projects/www.worldcommunitygrid.org/wcg_beta3_img_6.47_windows_intelx86__ati14_hcc1 X0000038271121200409250010.jp2 INFO: gpu_type not found in init_data.xml. INFO: GPU device not specified in init_data.xml. Checking Commandline. ERROR: GPU device not specified in init_data.xml or on command line. Exiting. 16:17:21 (3404): called boinc_finish </stderr_txt> ]]> ========================================== 1 Errored out with this message <core_client_version>6.10.18</core_client_version> <![CDATA[ <message> No process is on the other end of the pipe. (0xe9) - exit code 233 (0xe9) </message> <stderr_txt> </stderr_txt> ]]> I'm running Windows Vista Ultimate x64 Steve |
||
|
|