Few of my crunchers have fallen back on Einstein. And looks as though the beer companies in Juan's neighborhood would be a happy lot.
______________

I just hope they stuff some more tapes in the slot soon...

---

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

Totaly out of MB work and no one left on cache, my RAC now will fall as an asteroid!

Panic Mode ON...

I belive is better to go to buy some more beer, this will be a long weekend...

You do have AP on GPU enabled, no?
I now have 943 of them....no rest for my GPUs.

You might want to try putting some parameters in your ap_cmdline_win_x86_SSE2_OpenCL_NV.txt file, the following is a good start:

-unroll 10 -ffa_block 6144 -ffa_block_fetch 1536

Claggy

I just hope they stuff some more tapes in the slot soon...

One just loaded.

---

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

I just hope they stuff some more tapes in the slot soon...

One just loaded.

Unfortunately nothing is being split.
Current result creation rate is 0.2658 (ie 0), and has been for several hours. Almost all of my requsts for work are for the last 5+ hours are resulting in "project has no tasks avalable" messages, with just the odd one or two getting work- often only 1 WU.
I think something's jammed up somewhere.

---

Grant
Darwin NT

You might want to try putting some parameters in your ap_cmdline_win_x86_SSE2_OpenCL_NV.txt file, the following is a good start:

-unroll 10 -ffa_block 6144 -ffa_block_fetch 1536

Claggy

I've got a GTX 680 and a Quadro K2000M, each of which has loads and loads of memory.

I run two tasks simultaneously on both.

Is there any way I can put all that memory to use? I've set

-unroll 12 -ffa_block 8192 -ffa_block_fetch 4096

on both, as recommended in the readme.

Is there anything to gain from increasing those values further?

---

I just hope they stuff some more tapes in the slot soon...

One just loaded.

Still no new AP or MB work, now all my 3 fastest hosts are running empty of GPU work. The good thing is my power drain drops more than 1.5 kw at least. So i could save some money to buy more beers.

---

Unfortunately nothing is being split.
Current result creation rate is 0.2658 (ie 0), and has been for several hours. Almost all of my requsts for work are for the last 5+ hours are resulting in "project has no tasks avalable" messages, with just the odd one or two getting work- often only 1 WU.
I think something's jammed up somewhere.

One good thing about the extra run time is that the limited cache lasts longer.
Even with that, at the present rate i'll be out of work before nightfall if the splitters don't start splitting again.

---

Grant
Darwin NT

No work since this morning, any problems?

No work since this morning, any problems?

The splitters aren't splitting.

---

Grant
Darwin NT

One good thing about the extra run time is that the limited cache lasts longer.
Even with that, at the present rate i'll be out of work before nightfall if the splitters don't start splitting again.

Looks like i'll be out of GPU work by lunch time.
Won't help the plummeting RAC at all.

---

Grant
Darwin NT

One good thing about the extra run time is that the limited cache lasts longer.
Even with that, at the present rate i'll be out of work before nightfall if the splitters don't start splitting again.

Looks like i'll be out of GPU work by lunch time.
Won't help the plummeting RAC at all.

My 660's have been out of SETI work for 3hrs now and my 550Ti's just switched over to their backup project. :-(

Cheers.

If someone in the loop could let the staff know there's a problem with the splitters before they knock off for the weekend it would be appreciated.

---

Grant
Darwin NT

Just about out of GPU work. Didn't even make to close to lunch.

The splitters certainly are having issues, on the Server Status page sometimes all but one shows as green, then it's mostly red. Even when they are running 10/s is the most i've seen in the last 24hours or so. Even with the reduced load of v7 20/s seems to be the minimum to meet demand & still build up (although very slowly) a ready-to-send buffer.


Ever since the MB splitters were converted to PFB their output has been seriously limited. With several of them now repeatedly failing that limited output is making things even worse.



EDIT- i should have posted earlier.
The *very* second i hit OK for this post, i got 59 WUs for one of my systems GPUs. Another couple of hundred WUs all round & i should be good till tomorrow.

---

Grant
Darwin NT

I did an upgrade to BOINC 7.0.64 earlier today. Imagine my surprise when I could not get any work afterward. However, I did got 4 AP tasks a few hours later.

(there is always Einstein work if you feel neglected by seti)

---

I did an upgrade to BOINC 7.0.64 earlier today. Imagine my surprise when I could not get any work afterward. However, I did got 4 AP tasks a few hours later.

(there is always Einstein work if you feel neglected by seti)

I haven't read through this whole thread carefully, so ignore me if I say something stupid. I'd better amend that: Ignore me if I say something even more stupid than you would expect.

You did go to Preferences and enable v7 work, didn't you?

I did an upgrade to BOINC 7.0.64 earlier today. Imagine my surprise when I could not get any work afterward. However, I did got 4 AP tasks a few hours later.

If you upgraded from BOINC v6 you need to swap the values around in the cache settings. They changed in v7.

---

Grant
Darwin NT

I did an upgrade to BOINC 7.0.64 earlier today. Imagine my surprise when I could not get any work afterward. However, I did got 4 AP tasks a few hours later.

If you upgraded from BOINC v6 you need to swap the values around in the cache settings. They changed in v7.

No, the cache settings changed between BOINC v5 and v6.
There was a change early in BOINC v7 that affected flops/APR, but not cache settings.
Yeah, here is is, and it mostly applies to Anonymous Platform apps.

---

Donald
Infernal Optimist / Submariner, retired

If you upgraded from BOINC v6 you need to swap the values around in the cache settings. They changed in v7.

No, the cache settings changed between BOINC v5 and v6.

No, in BOINC 6 the amount of work BOINC asked for was minimum + additional, and it'd ask for it at any time that work was reported. In BOINC 7, we have the minimum + additional amount, but BOINC only asks for work after it's gotten below the minimum mark.

This means that when you have left your old BOINC 6 values for "Connect to" + "Additional work" at, example given 0.1 and 1.0, that BOINC 7.0 will ask for 1.1 days worth of work and ONLY renew this cache when it's fallen under the 0.1 days worth of work limit. Which means that it can happen that your BOINC runs empty, because 7.0 won't request new work before it has dropped below the 'minimum work' setting and will only ask for work up to the 'and additional' setting --and that only from the project that has the highest priority (worst REC to resource share ratio). Only if that project doesn't have work it will ask other projects in order of priority.

By changing the values around, 1.0 and 0.1, the minimum is 1.0 days. So when BOINC finds the cache falls under that value, it'll ask for new work and top it off to 1.1 or more days of work.

---

I did an upgrade to BOINC 7.0.64 earlier today. Imagine my surprise when I could not get any work afterward. However, I did got 4 AP tasks a few hours later.

(there is always Einstein work if you feel neglected by seti)

I haven't read through this whole thread carefully, so ignore me if I say something stupid. I'd better amend that: Ignore me if I say something even more stupid than you would expect.

You did go to Preferences and enable v7 work, didn't you?

Everything is working fine. A few hours after I posted, I got a bunch of seti 7 work for cpu and gpu.


Also, regarding upgrading. I upgraded from 7.0.25 to 7.0.64. So I was running BOINC 7 all along.

---