Tomorrow I'll post explaining why we wanted version 7 and what's different about the analysis it does.

So... what changed? I'm waiting for that post :)
I'm very curious about it!

I see i'm not alone who is curious :D

---

I have sent a message to Eric telling him that we are all very interested in his explanations about v7.

I know he was really, really stretched thin during the first few days of the conversion. But I don't know what else he may have had on his plate this week or if he is in the lab.

I know he intended to post about it before this. Please give him time......

---

"Time is simply the mechanism that keeps everything from happening all at once."

I'd like to get a hint of why v7 and Lunatics v7 are 30% slower on my Cuda5?

I'd like to get a hint of why v7 and Lunatics v7 are 30% slower on my Cuda5?

Confirm this. I don't know precition value 30% or other but slower

I'd like to get a hint of why v7 and Lunatics v7 are 30% slower on my Cuda5?

Mostly because of additional processing with v7 vs v6. And 30% is (IMO) below average. Even "shorties" on my 5xx GPU's are running double or more the previous times.

---

I'd like to get a hint of why v7 and Lunatics v7 are 30% slower on my Cuda5?

Mostly because of additional processing with v7 vs v6. And 30% is (IMO) below average. Even "shorties" on my 5xx GPU's are running double or more the previous times.

The extra amount of processing required is pretty constant across all ARs. So it actually shows up most (it's a higher %age increase) for shorties - it's less noticeable at lower ARs.

But I don't know what else he may have had on his plate this week or if he is in the lab.

There is the 222nd meeting of the American Astronomical Society this week in Indianapolis.
See an article mentioning it here

---

"It is often darkest just before it turns completely black."

I getting a notice to upgrade the gpu. I also keep getting computation error on everything. Anyone know whats going on

I getting a notice to upgrade the gpu. I also keep getting computation error on everything. Anyone know whats going on

A notice to upgrade the GPU? From where or what? I don't think Boinc has any such messages.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Old video hardware, older driver.
Error message on the errored WUs- too many exits.

---

Grant
Darwin NT

I'd like to get a hint of why v7 and Lunatics v7 are 30% slower on my Cuda5?

Mostly because of additional processing with v7 vs v6. And 30% is (IMO) below average. Even "shorties" on my 5xx GPU's are running double or more the previous times.

Hmmm... Even my Geforce GTX 650 (2 GB GDDR5) is now 30% SLOWER!!! :(

If you care to look through "number crunching" you will find an explanation (several threads) - In short, there are some new "features" added which add an overhead to the task duration, the processing time for these far exceeds the performance gain from the core task.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

If you care to look through "number crunching" you will find an explanation (several threads) - In short, there are some new "features" added which add an overhead to the task duration, the processing time for these far exceeds the performance gain from the core task.

Well... I can also tell it much easier: SHIT CODE! :p
Please give us back v6!

If you care to look through "number crunching" you will find an explanation (several threads) - In short, there are some new "features" added which add an overhead to the task duration, the processing time for these far exceeds the performance gain from the core task.

Well... I can also tell it much easier: SHIT CODE! :p
Please give us back v6!

I would say some actively refuse to read and understand what other wrote.
NEW SEARCH ADDED ! Comprehend ?

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Wasting GPU power for nothing --> disabled

Maybe some months later again if they fix the worst bugs!

Wasting GPU power for nothing --> disabled

Maybe some months later again if they fix the worst bugs!

You're not wasting GPU power, you're producing good science with your GPU, you haven't errored any GPU tasks out, so you haven't encountered any Bugs:

All tasks for computer 6504517

Application details for host 6504517

Just because the the autocorrection code isn't ultra fast doesn't mean it's Buggy, it's just New,
expect over the next couple of years that the autocorrection code, as well as a lot of the other code will get further optimised as the volunteer developers experiment,
and if it wasn't for the volunteer developers, we would only have v7 CPU apps and slower CPU apps at that.

When you're devised a better method of doing the autocorrection search please let us know, then it can be fed back into the source.

Claggy

Wasting GPU power for nothing --> disabled

Maybe some months later again if they fix the worst bugs!

You're not wasting GPU power, you're producing good science with your GPU, you haven't errored any GPU tasks out, so you haven't encountered any Bugs,

Just because the the autocorrection code isn't ultra fast doesn't mean it's Buggy, it's just New,
expect over the next couple of years that the autocorrection code, as well as a lot of the other code will get further optimised as the volunteer developers experiment,
and if it wasn't for the volunteer developers, we would only have v7 CPU apps and slower CPU apps at that.

When you're devised a better method of doing the autocorrection search please let us know, then it can be fed back into the source.

Claggy

Well said Claggy ! +100 !!!
I love >>

You're not wasting GPU power, you're producing good science with your GPU

For my part, I spend at NVIDIA next week ! Finally ! :)

---

When you're devised a better method of doing the autocorrection search please let us know, then it can be fed back into the source.

Claggy

Well... I would also help if I could, so give me your source! :p

(Yes, I'm assembler programmer already 30 years. And bugs not only create errors.)

When you're devised a better method of doing the autocorrection search please let us know, then it can be fed back into the source.

Claggy

Well... I would also help if I could, so give me your source! :p

(Yes, I'm assembler programmer already 30 years. And bugs not only create errors.)

It's on the front page, Porting and optimizing SETI@home

You want the XBranch for the Cuda app: branches/sah_v7_opt @ 1862

Claggy

I think it's autocorrelation not autocorrection ;-)

Gruß,
Gundolf