I started a new thread for this.

What applies for GPUGRID should apply for Seti.
So, 280 is the current fastest card.

gdf

Maybe, but I do not think their application is as intensive as GPUGRID. I tried to follow along in their forum but there is so much to read. They do not really need the fastest.

I think they have a shorter run time 2-3 hours for GPU's and probably can make use of slower cards not able to participate here.

It seems their deadline is about three weeks, 1/8/2009 for one downloaded a few hours ago, my first. But I still have to wait 8 hours for my current GPUGRID task to finish. Can't tell run length since it is the first it has an estimate of 00:00:00. I'm going to test a very few, but ultimately I will stay with GPUGRID and only use SETI@home as a backup should this project run dry of work, which seems to happen once and a while. Same for other projects as they come online.

I'll let you know how one compares after it completes.

I see they have windows only so far, and it appears their windows app only uses 4% or less of the CPU on windows. Currently the GPUGRID I'm running is showing 37 to 44.

Join team USA

On my System is very more CPU usage @GPU-Grid
The usage @seti is similar.

But I think, it's not necessary except for people with more than one GPU.

GPUGRID needs 0.90 CPUs, and SETI 0.03 ... so if you have to cards, GPUGRID takes 1.80 CPUs and SETI just 0.06. That means, that GPUGRID takes 2 CPU cores, same time as seti takes 1 core.


The Credits at SETI are still in Pendings, and won't get granted so fast.
Don't forget that SETI does this GPU-Computing till this WE and not as long als GPUGRID.

So I would prefer GPUGRID so far for people who wants to help or get Credits.
I decided to myself that I crunsh the two projects at 50:50. So I get enough Credits from GPUGRID and can help the SETI-People with theyre BETA-thing.

I got a couple returned results.

interesting parts:
Flopcounter: 28798913900607.105000

They do not record GPUtime, so it is hard to tell exactly.

Best guess would be 70-73 credits claimed (none granted yet) for previous approximate 26 minutes work. This estimates out to about 2665 credits for 16.5 hours, whereas GPUGRID here will grant 3232 for same time (based on my system). Of course credit is granted per flops computed, but you get more from here per time used.

@GDF
How many Flops are in your tasks ?
I know there are 850,000 steps, but how many flops in each step.

This way we could better compare the applications performance.

I ran some over there too & had it figured about 420 Per Hour where I get about 600 Per Hour here on the same Box with a Overclocked GTX 260 (216 Version) ...

I got a couple returned results.

interesting parts:
Flopcounter: 28798913900607.105000

They do not record GPUtime, so it is hard to tell exactly.

Best guess would be 70-73 credits claimed (none granted yet) for previous approximate 26 minutes work. This estimates out to about 2665 credits for 16.5 hours, whereas GPUGRID here will grant 3232 for same time (based on my system). Of course credit is granted per flops computed, but you get more from here per time used.

@GDF
How many Flops are in your tasks ?
I know there are 850,000 steps, but how many flops in each step.

This way we could better compare the applications performance.

A thing that I like from SETI is that you can have a lot of units in cache (which seems to contrdict the statement that it is BOINC, not GPUGRID that limit WU to 1 by each CPU)