Just found this on FF, its an interesting read. Whats even better are some of Vijays responses.
http://foldingforum.org/viewtopic.php?f=16&t=16375&start=0
http://foldingforum.org/viewtopic.php?f=16&t=16375&start=0
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Vijay's point #5 is very encouraging. Finally, something relatively soon will be forthcoming for Ati. /crosses fingers
Getting a good ATI client running might entice me to start folding again. Might.
It's also this teams only hope to pass EVGA once again and regain our rightful position at #1
And hopefully in time for winter. Since it will enter beta testing fairly soon, I wonder how much longer it will take to enter open data so all of us can try it out. I can't afford the extra power draw right now, but will make other sacrifices if the ppd/watt ratio is very good. Maybe we will get an ATI GPU3 client before the ATI Cayman and Cayman XT hit retail later this year. Of course i'm only dreaming..........
I still have three 4xxx and one 5xxx AMD/ATI card(s) waiting for this. It's not worth sucking CPU cycles to get 4K PPD from my 5870 at this point, but it is a far quieter and cooler card than my GTX 470 which I refuse to have in my office/main rig for this reason.
Just found this on FF, its an interesting read. Whats even better are some of Vijays responses.
http://foldingforum.org/viewtopic.php?f=16&t=16375&start=0
Well damn, you pulled a 6701.
I hate those things as my 980x gets lower ppd with those when my Bloomfield pulls a bigadv.
1. Running a benchmark before each unit would take time and would waste a considerable amount of CPU resources just for the sake of keeping the points system in check. That would not be practical.thats basically what we have been preaching since day 1 of the smp client release.. it will work.. he seems to think people can cheat on it.. but the way you stop cheaters is by making the client run a benchmark every time its started instead of a single time when the person could say overclock their processor to 4.5ghz long enough to run the benchmark, restart and put it back at 4ghz or 3.8ghz and double their points.. thats really what Vijays worried about but there are ways to stop that..
The idea is to run a benchmark on each individual computer so the client can generate appropriate PPD figures itself, rather than comparing performance to Stanford's own benchmark machine. However, I think that concept has too many flaws in it to be successful.Why run benchmarks? Do they not already have a performance fraction, updated every work unit?
They are sitting on a sea of real world benchmark data already.
Stanford runs every new unit on the benchmark machine to figure out how long it takes. Points values for each unit are then generated based on a target PPD level and the amount of time recorded. That's why the benchmark machine is needed.Agreed. I just wonder why we need benchmark machines at all, when every unit is already being timed.
I believe they revised their benchmarking method between when they did the original A3 SMP units and when they benchmarked 6701 and 6702.I read that, but bigadv units are all treated at the same PPD for the same time per frame - not much benchmarking going on there. It is like they benched the 2684 then just sent the 2685/6/92 out into the world.
That would also imply that somewhere, somebody on the same type of machine as they bench on would find 6701s as equally good as 6060. Would it not?
1. Running a benchmark before each unit would take time and would waste a considerable amount of CPU resources just for the sake of keeping the points system in check. That would not be practical.
2. Running a benchmark at a high speed and then going to a slower one for general use would actually decrease the amount of points you get, since your F@H performance would be below par compared to the benchmark speed.
The main problem with the benchmark system is that the PG use machines which isn't always what most people will use, under a OS rarely used by everyone. It might be very consistent for the PG but when different machines crunch them, we see discrepancies.
A better method would be to have a pool of 10 benchmark machines benchmarking a given WU then do some calculation to get a good points value which can show a variation in ppd less than 5-10%. Like that, it get closer to expectations everyone have in terms of ppd.
Those units were used to test the accuracy of calculations, not to test performance. Big difference. Running a benchmark just for performance testing would be a waste of resources as far as the project is concerned.1a. no it wouldnt waste resources because you still get a base value points for the benchmark.. i mean hell you have been doing this long enough.. so im pretty sure you remember the days when 9 out of the 10 WU's we were running on GPU's werent even for science they were just test WU's..
Is it just me or is that 7im character dumber (with an emphasis on the "b") than a bag of hammers rusting in the rain used to beat a bag of crap?
I mean what a brainwashed folding fanboy if I've ever seen one. Sorry about the off-topic mini-rant but he can't hold an argument worth its weight in dog feces and is so out of touch with everyone around him....
What is his connection to the folding@home project outside of beta testing anyway?
Sheesh.
This right here is making me drool thinking of the possibilities if we only had a decent ATI client.
If you think Stanford is being paid off by nVidia, you need to take off the tinfoil hat, because it must be microwaving your brain .Unfortunately, I feel Stanford is in the same pocket as Evga!
There already is an ATI client.Don't see an ATi client any time soon! But I hope I'm wrong!
If you think Stanford is being paid off by nVidia, you need to take off the tinfoil hat, because it must be microwaving your brain .
There already is an ATI client.
I know what he meant, but it's not what he said, and the distinction between the two is an incredibly important one.Gary means an ATI client that isn't a POS you smartass
vijaypande said:ATI deprecated their GPU language, Brook, in favor of OpenCL. So, we were forced to completely rewrite our GPU core for ATI in openCL. This takes time, especially to write highly optimized code. We have been internally testing this and expect to start beta testing it shortly (days to weeks). It will require client changes that are now built into the v7 client.
Well, in June he said we'd probably see an open beta in a "couple months".. it's been more than a couple months. PG's time estimates are always skewed.He also said that he expects v7 client by the end of the year or sooner.
let me guess. The next one will be "when it's done"Well, in June he said we'd probably see an open beta in a "couple months".. it's been more than a couple months. PG's time estimates are always skewed.
wait, doesn't that happen every year? I hear it's in Michigan.LOL the phrase "soon" has its own meaning in the programming world.
It could mean tommorw. or it could mean when hell freezes over.