Posts by Henk

1) Message boards : News : Scheduled Maintenance Concluded (Message 65721) Posted 12 Nov 2016 by Henk Post: Hey everyone, i'm a first day newbie in milkyway (POEM finished the project, so i was lookin for another gpu-project with AMD support), but i'm also a distributed computing user since 1999... My first thoughts after attaching to project were "nice, it downloaded cpu and gpu tasks fromt the same batch, let's see how my one week old AMD RX 480 performs, especially regarding to the DP mode and how the gpu- and cpu perform against each other..." example of wu: Milkyway@Home 0,751C + 1 AMD/ATI GPU 1.42 milkyway (opencl_ati_101) de_modfit_fast_19_3s_136_bundle5_ModfitConstraints3_3_1478900148_101814_0 next thought was "wtf???" to keep it short: the gpu-tasks take as long (~) as the cpu-tasks, the gpu is completely unemployed (2% avg. gpu and memory controller load), the wu well finshes, but avg cpu load per wu is 99,8% - on a gpu-task! OK, the FX-8320E isn't a hell of a machine and i read then in the forum that this client runs better with more than one gpu-task assigned to a gpu, but 10 times 2% is still just 20% gpu-load, but with the need of simultaneously 20 cores??? c'mon my FX8320E isn't that bad ;-) I was close to desperation, wondering myself if this would be my first project wich i immediately deteach from or if i should crunch just the cpu-tasks, but at last i found this thread and now calmed down because of "oh bad luck at the beginning, seems to be a faulty new client version 1.42" . So thx4information and until it's solved i guess i have to wake up my gpu with einstein ;) So, ehrm, jepp, can confirm exactly the same behaviour like in post 65714-65716 and so on.