Message boards :
Number crunching :
Problems with running 1 wu per AMD Radeon gpu , app_config.xml
Message board moderation
Author | Message |
---|---|
The_Matrix Send message Joined: 17 Nov 03 Posts: 414 Credit: 5,827,850 RAC: 0 |
Hello heres no problem, the problem is solved. But i want to write about it. I am got a Radeon HD 6950, and the crunshing of one wu was stuck. It ran so slowly so i have to quit crunshing, but that wasn´t the solution. Just as i gave the gpu more wus to crunsh it constantly and automaticly crunshes the right way. See this: not new but it helped. <app_config> <app> <name>setiathome_v7</name> <gpu_versions> <gpu_usage>.25</gpu_usage> <cpu_usage>.5</cpu_usage> </gpu_versions> </app> </app_config> Any optimizions needed ? Greetings |
Mike Send message Joined: 17 Feb 01 Posts: 34253 Credit: 79,922,639 RAC: 80 |
First of all Cat 12.4 always caused problems on my Sons PC with 6850. I upgraded it to 12.6. Yes, the HD 6 series indeed needs more CPU than HD 5 and HD7 cards. One reason i always suggest to free at least one CPU core. With each crime and every kindness we birth our future. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I had issues with Cat 12.x as well with my 6870 & ended up going back to Cat 11.12 for a long time. Then went with Cat 13.4+ & am using Cat 14.4 now with no issues. I seem to recall MB tasks would sometimes hang & run very long time. It could be 10+ hours later to find task 20% complete. Back then it could have been older app, older driver, or both. Also found performance of my 6870 increased after upgrading system from Core 2 Duo E8400 to i5-4670K. I think maybe something in core 2 system was causing bottleneck for video card. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
FalconFly Send message Joined: 5 Oct 99 Posts: 394 Credit: 18,053,892 RAC: 0 |
I still wonder if the GPU tasks are getting enough priority when the CPU is also loaded with CPU tasks. Plus, the default numbers for typical GPUs are like <avg_cpus>0.04 and <max_cpus>0.2 That always seemed a little low, I prefer a fixed 0.5 avg_cpus/max_cpus for 2 tasks/GPU, respectively 1.0 avg_cpus/max_cpus for a GPU running a single task. In all cases, reserving one CPU core for each GPU running seemed to yield far better performance. Must say though, compared to the older BOINC versions (where anything below 1.0 would cause GPU tasks to just hang idle due to almost never getting CPU time), things have improved alot with the current BOINC version. |
The_Matrix Send message Joined: 17 Nov 03 Posts: 414 Credit: 5,827,850 RAC: 0 |
then the driver version must be my fault, i will load 14.4 and see :) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I'm still having wake from sleep issues with Windows 8.1, Catalyst 13.12, 14.4, and Beta 14.7. I don't recall having this problem with 13.4 last year. The worst one is by far 14.4. 13.12 was good until the summer thunderstorms started, then I discovered a bad wake from Hybrid Sleep issue. I turned off Hybrid Sleep and then the regular wake from sleep issue seemed to worsen. Since 14.6 worked so well in Linux I decided to try that. Alas 14.6 was history so I went with 14.7. Catalyst 14.7 seems to work best with the exception of the wake from sleep issue once or twice a week. The number of Inconclusives are way down with 14.6 & 14.7 on Windows 8.1 and Ubuntu 12.04. Hopefully 14.8 will solve the wake from sleep issue with Windows 8.1... |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.