Tapes are beginning to appear, slowly. IIRC, there's quite a long pre-processing phase, which we don't see: as they emerge from that, they pop up automatically in the splitter queue.

Tapes are beginning to appear, slowly. IIRC, there's quite a long pre-processing phase, which we don't see: as they emerge from that, they pop up automatically in the splitter queue.

Well done, Eric and Jeff!

---

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

Looks like break time is over. Work is starting to slowly build up again.

---

~Chris

I wonder if they could sort the database and move most of it into an archive database. All the work that is done and has nothing left in the field, thus leaving a much more manageable database active and online. Then the weekly outage would just sort the active database and move whatever has been completed during the week to the archive.

I know this sounds too simple to be possible, but might that be possible? Some database inquiries would have to be rewritten to access the archived information.

I dunno, just spitballing.

Meow?

+1

---

Hello,
Everytime then the WU are withdrown, my crunchers encounts the same behavior: the slower & less core one, which has few WU's left to crunch, receives new WUs , before the second cruncher (faster & more cores) which is totally withdrown of CPU WUs , receive it's new batch. Also when it receivs it got first GPUs (which some are already from the previous batch) and no CPU WUs. How schould I configure it for letting more CPU WUs be downloaded in advance instead of GPUs? Every outrage I would need some 100 CPU WUs more to have the work sustained on the faster machine.

Results ready to send : one ????
EDIT: Just changed to zero.

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

Hello,
Everytime then the WU are withdrown, my crunchers encounts the same behavior: the slower & less core one, which has few WU's left to crunch, receives new WUs , before the second cruncher (faster & more cores) which is totally withdrown of CPU WUs , receive it's new batch. Also when it receivs it got first GPUs (which some are already from the previous batch) and no CPU WUs. How schould I configure it for letting more CPU WUs be downloaded in advance instead of GPUs? Every outrage I would need some 100 CPU WUs more to have the work sustained on the faster machine.

Generally, if you allow both CPU and GPU work, the servers determine which to send you. You can temporarily turn off fetching of GPU WUs in BOINC (in Advanced mode) under the Activity tab. Until you turn GPU fetch back on, you will get only CPU WUs.

---

So would now be a good time to panic?? ;)

Just kidding....why I have back up projects. Giving beta a test, thought I'm not sure what we are looking at there...(only 1 machine and only 1 work unit per card)...Einstein is getting a boost from this.

---

My backup project is to improve the code and run local tests.

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

My backup project is to improve the code and run local tests.

Recovering some of those 5,300+ ghosts you've created wouldn't be a bad use of your time, either. Having those locked away when other people are starving for work is not particularly helpful.

How does one have so many errors and invalids?

He is testing a cuda alpha application, so there is bound to be some teething issues.

---

Ah ok, ty for reply

How does one have so many errors and invalids?

. . By being a developer (Petri) and constantly trying new things ... or in other cases by having faulty hardware or totally misconfigured apps that trash most of the WUs you receive, there are many of them around too.

Stephen

:)

Is it just me, or are these new 02 WUs processing even faster than the previous 05s? Around 10sec on the GPUs and 4min on the CPU faster.
The servers weren't doing too well as it was, these new WUs will push them even harder.

---

Grant
Darwin NT

Id say your right Grant..

Looks like we've reached that critical point of returned-last-hour, WU-waiting-deletion, in-progress and splitter load.
Waiting-deletion is going up, splitter output has gone down, and Ready-to-send buffer is rapidly emptying. And with the shorter WU run times, channels left to be split is rapidly diminishing also.

---

Grant
Darwin NT

Eric muttered something in Beta a few days ago about finalising some "new binaries" that might be loaded onto the servers this Tuesday - perhaps he wants to have a fairly low RTS before doing the update....

---

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

Eric muttered something in Beta a few days ago about finalising some "new binaries" that might be loaded onto the servers this Tuesday - perhaps he wants to have a fairly low RTS before doing the update....

I hope the implementation is smoother here than at Beta.

---

Grant
Darwin NT

Eric muttered something in Beta a few days ago about finalising some "new binaries" that might be loaded onto the servers this Tuesday - perhaps he wants to have a fairly low RTS before doing the update....

I hope the implementation is smoother here than at Beta.

No new applications have appeared on the Beta applications page since October 2017, and those were all for Mac - so whatever the current problems are at Beta, it can't be attributed to new application binaries.

What Eric actually said was

We're testing BOINC updates, which have broken the splitters.

We'll probably promote these server binaries to the main project next week.