Forum > GPU crunching
ATI OpenCL AstroPulse (rev516) released
Raistmer:
--- Quote from: Ghost on 18 Mar 2011, 03:20:58 pm ---Didn't think it mattered was just wondering if there was a reason?
(And it broke my task monitoring app :o)
--- End quote ---
No reason besides some inaccuracy :) I took app_info section right from my production PC. And there I don;t care much for meaningless numbers :)
Also, I think flops section can/should (?) be omitted too now? Any opinions on flops ?
Ghost0210:
I;ve only got them in becuase I'm currently running 6.12.18 and the v7 app @ beta and didn't want that app screwing up the rest of my times for my other tasks there
If it weren't for that I wouldn't bother either anymore
Edit: another quick question - with the app_info the plan_class doesn't get used either does it (I can't use standard plan_class as need a way to differentiate between Seti & Beta tasks)
Raistmer:
what do you want to use instead of ati13ati then ??
Ghost0210:
--- Quote from: Raistmer on 18 Mar 2011, 04:22:49 pm ---what do you want to use instead of ati13ati then ??
--- End quote ---
I use ati13ati for Seti tasks and ati13ati_beta for beta tasks (and yes, I've also given cpu tasks a plan_class @ Beta as well)
I got fed-up with Boinc Manager and wrote a small app that gives me pratically the same information with half the overhead of BM
Only reason I ever open BM now is to start and stop processing and do network comms
Problem is, Beta and Seti Main tasks are identical in the client_state, so to seperate them out in the app, so I could get accurate info I had to change either the version_num or the plan_class values. I chose the plan_class to change
As far as I can tell it's made no difference to work fetch and/or scheduling as I think this is all done from the coproc value
benool:
Seems to work great on my ATI 4550. :-*
I had to set -unroll 5 instead of 10 otherwise I get computation errors.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version