With DNetC now available which provides largely the same GPU support as Collatz, MW will drop down to my number three project in terms of TC within a couple of months. It is interesting the sort of reliability that Collatz and Dnetc can provide with quite limited resources (of course with lower user counts).

I guess we can hope that Travis is able to pass on the torch here to someone at RPI who will be 'invested' in the project as he was in the past. My other hope is that additional 'low end' GPU projects, particularly ATI GPU projects, start showing as well.

BarryAZ,
I'm afraid you're right. My hope is that someone follows his footsteps.

As I've learned from GPUGRID, cal is an 'outdated' programming tool. They are working on OpenCL Apps, which should be a step to an independency of the type of your card as long as it supports OpenCL.

Two or three month's ago somebody posted here in this forum, that other projects are working on GPU-Apps. Let's see if I can find that again.

Alexander

Yes, I got that -- if that is the 'permanent' plan for SETI, then the folks most affected by that are the 'SETI uber alles' crowd -- for that group, the self-imposed 'only one project' makes them dependent on a project that, aside from the newsgroups, runs only 50% of the time and is pretty well stressed with folks crowding into the 'half-space' for uploads and downloads.

The plus side is that the much smaller active BOINC crowd that might have originally been brought into distributed processing by SETI and doesn't have a 'SETI only' DP world view might well help out other projects which are not half time.

As I understand it, the 3 day outage is to let Nitpicker run on 10 years worth of results to sift for likely candidates to re-examine. When they tried it in real time it zonked the servers and the database out. You can't upload or download work for 3 days, but the message boards are only out for 9-12 hours as they were before.

---

I run a GTX260 24/7 on Seti. it is no big deal. I needed to adjust my cache to 4 days to assure constant work, but that's no big deal.

As to DnetC, I find it makes an excellent backup project for me. I am running it now on two, twin 5790 computers. One 5790 and 4770 computer. And one single 5790 computer, so it is pretty adaptable from my point of view.

OK must go MW just downloaded on one of the boxes, so lets see if I can get the others back!

---

hmm, i got some WU's, assimilation seems to be up and running. have to wait though. AFAICS, there are a small bunch ready to send.

Work is avilable again

---

Go away, I was asleep

no validation though

---

Blah blah blah you know the rest

no validation though

It may have still been catshing up with the backlog when you looked. The Validator backlog now reads 6,287 WUs

---

Go away, I was asleep

Looks like the root cause is either winning or being looked into -- web pages are on -- sort of in a SETI emulation mode we are at the moment.

---

Back to Collatz, which has good uptime since Comcast repaired/replaced parts of the BB line.

---

Go away, I was asleep

I just setup Collatz to be my primary project and Milky Way to be my backup. I really like Milky Way, but when you average in the downtime and the almost nonexistant cache, I am getting much better credit returns at Collatz.

If only I could get DNETC working om my system, I would set up as #1=DNETC, #2=Collatz, and #3=Milky Way.

I will keep checking back with the hope that I will find that the reliabilty of this project has improved.

Mike...

OK -- so could we PLEASE get some feedback from folks at the project as to what is going (or not going) on?

One thing more troublesome than outages is outages in a vacuum.

---

OK -- so could we PLEASE get some feedback from folks at the project as to what is going (or not going) on?

One thing more troublesome than outages is outages in a vacuum.

Erm..front page.

Now the Server Status page is beginning to look ominous regarding another validatior backing up problem.

When all is running smoothly the status page Workunits waiting for validation usually runs with between 6,250 and 6,4000 results waiting. I see the status now gives us with 12,139 waiting validation. If this continues then the whole shebang will be down again.

I have PMed Matthew as a precaution, which I hope I am wrong about.


[Edit mode on - 35 minutes after first posting this potential panic]

Thanks Matthew.

The validator is back to it's usual numbers waithing for validation.

PANIC avoided

[Edit mode off]

---

Go away, I was asleep

Knock knock!

---

Sending scheduler request: To fetch work.
Requesting new tasks for GPU
Scheduler request completed: got 0 new tasks
Message from project server: No work sent
Message from project server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

Is N-Body the only style of work being assigned now? Or is this just a glitch in the matrix?

Sending scheduler request: To fetch work.
Requesting new tasks for GPU
Scheduler request completed: got 0 new tasks
Message from project server: No work sent
Message from project server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

Is N-Body the only style of work being assigned now? Or is this just a glitch in the matrix?

I was getting the same thing, so I reset the project. It didn't help. The server page shows workunits available, but I am unable to get any of them.

They could be CPU N-Body workunits. But, the validator is backed up and looks like it is about to crash, also.

No panic boys, it is weekend....

Servers and validators have some days of too every now and then.

---

Greetings from,
TJ

OK -- so this problem -- which has shown up every week or so remains unresolved -- frankly, not really a surprise.

Sending scheduler request: To fetch work.
Requesting new tasks for GPU
Scheduler request completed: got 0 new tasks
Message from project server: No work sent
Message from project server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

Is N-Body the only style of work being assigned now? Or is this just a glitch in the matrix?

I was getting the same thing, so I reset the project. It didn't help. The server page shows workunits available, but I am unable to get any of them.

They could be CPU N-Body workunits. But, the validator is backed up and looks like it is about to crash, also.

---

It's the validator again - it has backed up with 59K worth of work to knock off.

---

Go away, I was asleep

Are the servers dishing up nBody work ATM?

---

Go away, I was asleep