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.

---

Once again the splitter output is falling away & ready-to-send buffer is slowly shrinking.

---

Grant
Darwin NT

Once again the splitter output is falling away & ready-to-send buffer is slowly shrinking.

Now it's a case of splitter output is next to nothing, work to split is almost used up, and ready-to-send buffer is rapidly dimishing.
Should be out of work in a few more hours.

---

Grant
Darwin NT

Jord,

What does the scheduler do if "Minimum work buffer" is set to 0 for BOINC v7.0.64?

---

Setting a zero minimum work buffer is one of the few things in the buffer setting that says what it means - your minimum work level will be zero - don't ask how I know, its embarrassing...

---

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

Setting a zero minimum work buffer is one of the few things in the buffer setting that says what it means - your minimum work level will be zero - don't ask how I know, its embarrassing...

Setting a Boinc 7 to a minimum work buffer of 0 translates into a target workbuffer of 180 - 3 minutes.
Setting the 'additional' work buffer to 0 does indeed give 0 additional cache.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Once again the splitter output is falling away & ready-to-send buffer is slowly shrinking.

Now it's a case of splitter output is next to nothing, work to split is almost used up, and ready-to-send buffer is rapidly dimishing.
Should be out of work in a few more hours.

Well, no more MB work available.
Will be out of GPU work before lunch.

---

Grant
Darwin NT

Don't know if i ran out or not, but those PFB splitters are really struggling.
Just not producing much work at all, although i notice there's been a lot of databse activity over the last few hours as well. May be blocking the splitters efforts?

---

Grant
Darwin NT

I'm still in a bit of a Power Dive, much like this Curtiss P40 Warhawk @ 661MPH!! WR!!(1941-video), got that ZERO in My sights...

I do expect to climb again, but it's gonna take some time after zapping that ZERO...

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Server status page is covered in Red. Although 3 PFB splitters are supposedly running, and there are tonnes of tapes ready to be split, no work is being produced.
Looking at a weekened without work? Hopefully not.

---

Grant
Darwin NT

AP splitters are down. Still 5 pfb splitters running. I am getting work no problem

Andy

---

Still 5 pfb splitters running.

Yet they aren't producing any work- current rate of production 0.6 WU/s. Needs to be around 20/s just to meet demand, let alone produce a ready-to-send buffer.

I am getting work no problem

Because there is a ready-to-send buffer (most of the time). Usually there are around 300,00 WUs in it, it's now down to 151,000 & falling steadily.
At the present rate there will be no work available in about 6 hours.

---

Grant
Darwin NT

Unless they fix whatever the problem is, we'll run dry of MB a bit after 0Z. AP an hour or so before then.

---

"Life is just nature's way of keeping meat fresh." - The Doctor

Unless they fix whatever the problem is, we'll run dry of MB a bit after 0Z. AP an hour or so before then.

And moments after that, life as we know it will end. Collective suicide?

I tried to shoot me a few minutes ago.

---

With each crime and every kindness we birth our future.

Almost out of MB & AP work.
Even less splitters running now, and they're producing as much work as when the others were running- none.


What is the problem with these splitters? Are they choking on certain tapes, or is it just some types of data that cause them to fail?

---

Grant
Darwin NT

Almost out of MB & AP work.
Even less splitters running now, and they're producing as much work as when the others were running- none.


What is the problem with these splitters? Are they choking on certain tapes, or is it just some types of data that cause them to fail?

Both of my machines have a full cache of GPU work.

---

So what's happening with the upload spikes then? I can't remember I ever saw the blue line any higher than 30Mbit on the old line. So spikes of 220Mbit are weird. :-)

---

Both of my machines have a full cache of GPU work.

So have mine, but it won't last when there is no more work available to download.


EDIT- luckily it's come back to life. Data is being split again.

---

Grant
Darwin NT