Did you look to see what the deadlines were for the APs vs the MBs?

It also depends on how fast you process the work units. If it thinks you won't finish the work by the deadline, it will move it to the front

Mine always run FIFO, unless I deliberately go in and tell it to run the APs first

Zalster

---

Ap's mostly have a shorter deadline.
However there are a few seti tasks, that have shorter deadlines than the AP tasks, that took over.
In any case, should the tasks not be marked "running high priority" as soon as the normal order is overruled?
Isn't that the purpose of marking tasks as "running high priority"?
It does not matter, how immediate the threat of not being finished in time is.

In any case, should the tasks not be marked "running high priority" as soon as the normal order is overruled?

Sorry, that statement just confused me.

Did you mean, that the task should be marked running as high priority?

I not sure what machine you are looking at, the 4 core or the 2 core. I'm guessing the 4 core.

I can't say for sure why it is doing that. You will have to wait for one of the others that understand the coding to answer that for you.

---

So long Boinc is still in EDF mode (early deadline mode first) the tasks won`t be marked as high priority.
Only if its getting close to the deadline.

---

With each crime and every kindness we birth our future.

What i meant is, that as soon as boinc changes the normal order of wu's to be run because it thinks, a wu's may not be finished in time, this qualifies the wu as running in "high priority" mode and should be labeled as such.

I guess, it all comes down to the fact, that SETI is the only boinc-project, that does not use edf in the first place, like all others do.

Has anybody else noticed a large number of inconclusive APs starting today?

---

I'm seeing 25 so far just from today but still have alot out on 3 other computers that haven't reported yet

---

I only use Seti on 1 computer and I now have 24 Ap's in the inconclusive bin. I cant remember that number being anywhere near that high before.

Bob

---

Sometimes I wonder, what happened to all the people I gave directions to?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SETI@home classic workunits 4,321
SETI@home classic CPU time 22,169 hours

I only use Seti on 1 computer and I now have 24 Ap's in the inconclusive bin. I cant remember that number being anywhere near that high before.

Bob

Have a look here:
http://setiathome.berkeley.edu/forum_thread.php?id=77774&postid=1706085#1706085

---

Aloha, Uli

Just for interest, since AP came back (on 27 July my time) I have:

240 Pending
81 Validation Inconclusive
280 Validation Pending
109 Valid

710 Total

In watching the machines, not one machine managed to get anywhere near the limits and one machine is now completely out (of AP and MB) and the others are drying up.

Now just have to wait till tomorrow ...

---

My GTX980 is cold since many hours. The CPU on the same machine still have some WU's, and the Intel HD4600 on the same machine have work for several days.

I had to turn the AC off haha

---

I came down with a bad case of i don't give a crap

All of my inconclusive APs are gone and I think they were validated, I hope.
4 mins ago I was able to report 11 APs and some validated. The ssp shows we are up and running with APs being split.

---

I'm seeing green across the board on the server, with the exception of the usual of course

---

Still nothing coming down the pipe, though. Getting pretty low now.

---

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

A proud member of the OFA (Old Farts Association)

7/29/2015 2:56:31 PM | SETI@home | Sending scheduler request: Requested by user.
7/29/2015 2:56:31 PM | SETI@home | Requesting new tasks for NVIDIA GPU
7/29/2015 2:56:33 PM | SETI@home | Scheduler request completed: got 0 new tasks
7/29/2015 2:56:33 PM | SETI@home | No tasks sent
7/29/2015 2:56:33 PM | SETI@home | Tasks for CPU are available, but your preferences are set to not accept them

and yet there are 14,960 AP's available and growing ... must all be CPU bound

Ed F

7/29/2015 2:56:31 PM | SETI@home | Sending scheduler request: Requested by user.
7/29/2015 2:56:31 PM | SETI@home | Requesting new tasks for NVIDIA GPU
7/29/2015 2:56:33 PM | SETI@home | Scheduler request completed: got 0 new tasks
7/29/2015 2:56:33 PM | SETI@home | No tasks sent
7/29/2015 2:56:33 PM | SETI@home | Tasks for CPU are available, but your preferences are set to not accept them

and yet there are 14,960 AP's available and growing ... must all be CPU bound

Ed F

Nope I am getting exactly the same asking for CPU tasks. probably just demand outstripping supply. Remember what matters is not the number ready to send but the number in the buffer and that is only around 100 if I recall. If someone else has just grabbed the lot before you then you will get nothing.

---

Thee SSP is now showing 16,042 APs ready to send

So close yet so far. sigh

Bob

---

Sometimes I wonder, what happened to all the people I gave directions to?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SETI@home classic workunits 4,321
SETI@home classic CPU time 22,169 hours

those are all for grumpy

It'll take forever and then some to download 19,000+ APs on that Swedish slow internet of yours. So why not step aside and let us with bigger connections get theirs first, shrimp? :-)

---