Juan, if the database is too slow, the servers would be unable to assign the already split files to a user, so nothing gets sent back to us.

If the database is slow (no matter why) my question is why we can´t get any WU if there are plenity of WU ready splitted on the cache?

That's where the slow down is, moving the WUs from the cache to the feeder. The Scheduler allocates work from the feeder to systems requesting work for download. If there's nothing in the feeder, the Scheduler can't give you any work- no matter how much there might be that's ready to send.

---

Grant
Darwin NT

And just as I typed that ... I see 120 tasks comming my way, of course on my slowest computer...
EDIT: Logjam clearing??? 80 on another computer ..

And just as I typed that ... I see 120 tasks comming my way, of course on my slowest computer...
EDIT: Logjam clearing??? 80 on another computer ..

Still nothing on either of mine.

---

Grant
Darwin NT

Ditto that for my 2 biggest computers - nothing but popcorn farts ...

Ditto that for my 2 biggest computers - nothing but popcorn farts ...

Typical. I should have posted sooner- 5 min after posting, I scored some work.
All shorties, one of them noisy to boot.
Should be out of GPU work in 30min, another 45 for the CPU. The C2D is that slow it'll probably have GPU work till tomorrow & the CPU for a day or 2 after that.

---

Grant
Darwin NT

One thing noticeably missing from manual updates is ... last request too recent ... so the database is either not recording task request, or not reading it ...

Whilst my 3570K rig is still keeping its head above water my 2500K rig has finally been able to fire its 1060's back up again.

BTW Sten, I'm enjoying some homemade dark rum here. ;-)

Cheers.

And just as I typed that ... I see 120 tasks comming my way, of course on my slowest computer...
EDIT: Logjam clearing??? 80 on another computer ..

Still nothing on either of mine.

. . I guess we need to wait for the trickle down ....

Stephen

<sigh>

One thing noticeably missing from manual updates is ... last request too recent ... so the database is either not recording task request, or not reading it ...

. . That is a concern for me as well, surely a sign something is not doing it's job when premature d/l requests are not even acknowledged as such. I will feel better when I begin to see that response again :)

Stephen

:(

Ditto that for my 2 biggest computers - nothing but popcorn farts ...

Typical. I should have posted sooner- 5 min after posting, I scored some work.
All shorties, one of them noisy to boot.
Should be out of GPU work in 30min, another 45 for the CPU. The C2D is that slow it'll probably have GPU work till tomorrow & the CPU for a day or 2 after that.

. . I wonder what the trigger word is that kicks off that eerie achievement ... still nothing coming my way ...

. . I just fired this rig back up and it is about to upload it's last task ... If that gets nothing then back to sleep it goes ....

Stephen

:(

. . I wonder what the trigger word is that kicks off that eerie achievement ...

ATM it's hitting the servers while something is in the feeder. ;-)

Cheers.

. . I wonder what the trigger word is that kicks off that eerie achievement ...

ATM it's hitting the servers while something is in the feeder. ;-)

Cheers.

. . Well clearly I cannot manage that because I am completely out of work, back to sleep for my rigs until tonight ... :(

Stephen

:(

Well you can't get work if they aren't running, and they use a LOT let power when empty, LOL.

Well I've had some success getting work on my slowest crunchers, but the Linux box and the Ryzen 1700X are still unable to get work. The Win10 box is doing lots of MW and Einstein in the meantime.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

CPU is cold, but GPU somehow keeps picking up dribs & drabs every now & then.
And better still the last bunch weren't all shorties.

---

Grant
Darwin NT

Ditto there Keith, my 1080 have been dry since this afternoon other that a few dribbles that rarely last until the next request - and lately nothing at all. And looks like my next biggest computer will be joining it again.
EDIT just when I hit enter ... 8 tasks, 10.5m estimate, divided by 3 = 3.5 LOL

Well, things are still broken, but they're not as broken as they were.
Every now and then my systems pick up a bit of work.

And the work-in-progress has stopped falling, and even moved back up, a bit.
But now it looks like there are issues with the splitters as well. Before, as the ready-to-send buffer emptied out, they would fire up & top it off. Now the ready-to-send buffer is emptying, and the splitters just aren't cranking up to meet the demand.
So as well as difficulty in getting work when it's available, another 6-8 hours and there won't even be much work available to send anyway.

---

Grant
Darwin NT

Well you can't get work if they aren't running, and they use a LOT let power when empty, LOL.

. . and even less again when off .. :)

. . I am willing to live with the pain when they are processing work but not when they are doing nothing ...

. . It seems there is no joy in Smurfville tonight, so I guess they will have the entire weekend off :(

Stephen

:(

Don't worry about it, Stephen, you are not missing much! I may still be running and have a reasonable amount of work, but now I can't report the tasks! Uploads, are fine, but that's as far as it goes.

---

Don't take life too seriously, as you'll never come out of it alive!