Aw shucks....
A new AP run, and I have over half the farm shut down all week due to the heat here.

Meowsigh.

Same story different venue..........Grrr.

---

"Sour Grapes make a bitter Whine." <(0)>

Got all the lights off and windows curtains pulled shut to try and keep it cool in here. 99 F outside

---

I'm slowly raking them in. My gluttonous ~18-day cache from the last frenzy ran out finally two days ago, so I'm starting to pull more back in. When requesting 2.6M seconds of work.. nothing was being given to me, so I have to keep adjusting the desired cache as I get more assigned, otherwise the server won't give me any. Om nom nom nom...

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I got 0

I got 1 AP task on Prometheus. (GTX-750 TI SC.)

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I'm slowly raking them in. My gluttonous ~18-day cache from the last frenzy ran out finally two days ago, so I'm starting to pull more back in. When requesting 2.6M seconds of work.. nothing was being given to me, so I have to keep adjusting the desired cache as I get more assigned, otherwise the server won't give me any. Om nom nom nom...

I noticed that you are only running CPU tasks. In my experience, it takes longer to get CPU tasks then it does to get GPU tasks, but I can't give you a reason why this happens outside of the fact that there were no CPU tasks ready when the scheduler told me it was my turn. During the last feeding frenzy I had a full GPU cache of 200, over several days, before I saw my first CPU task. I do have a question - Are you accepting other applications when AP is not available?

---

I don't buy computers, I build them!!

I'm slowly raking them in. My gluttonous ~18-day cache from the last frenzy ran out finally two days ago, so I'm starting to pull more back in. When requesting 2.6M seconds of work.. nothing was being given to me, so I have to keep adjusting the desired cache as I get more assigned, otherwise the server won't give me any. Om nom nom nom...

I noticed that you are only running CPU tasks. In my experience, it takes longer to get CPU tasks then it does to get GPU tasks, but I can't give you a reason why this happens outside of the fact that there were no CPU tasks ready when the scheduler told me it was my turn. During the last feeding frenzy I had a full GPU cache of 200, over several days, before I saw my first CPU task.

I know I remember reading some comments that GPUs tend to fill first/faster than CPUs in a mixed system, but I've never generally had a problem getting work. I don't get 20 tasks in one request, but I generally get 1-3, sometimes upwards of 5. It's all luck of the draw, methinks. Presently, I'm on six consecutive "no tasks available" replies.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I've shut off getting MB while AP is flowing. When the flow completely stops, I'll turn them back on again. Right now I have 40.

---

I don't buy computers, I build them!!

It's much better than it used to be.

At least now I get some, where a few months ago I could go days before an AP showed up.

I'm not complaining. Loving the APs

---

I still got 0. Lol.

I've got a few

---

I've picked up 45 so far. The pattern seems to be 1-3 "no tasks available for APv7" and then being granted 1-4 WUs maybe two requests in a row, and repeat.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Let me check again... Yes yes here we g... No. Never mind. Still none.

Let me check again... Yes yes here we g... No. Never mind. Still none.

Bad luck, I suppose. The luck of the draw doesn't appear to favor you. I've gathered 80 thus far (though a few have been 100% blanked B3_P1's, so I turn those around to get them out of the way), and still have more room in the cache before hitting the hard limit of 100.

A good chunk of the work I've gotten so far has been rather heavily blanked, as well, so instead of ~10 hours for each task, they're ranging from 1.5-5 hours instead.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

The only thing I can say really is:

Nom, nom, nom. :-)

Agreed. I'm nearly up to the 100-task limit. This has been another good feeding cycle, and there's still many more tapes to go.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

116 here so far, now just to get rid of a few more VLAR's so I can hit 200 again.

Cheers.

iv managed to get 81 on one computer and 66 on the other lol.
keep them coming,they will chew them up.

Exeter, (GTX-760), FINALLY picked up 2. :-)

Prometheus, (GTX-750 TI SC), finished it's first yesterday, and now has 2 more. :-)

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Let me check again... Yes yes here we g... No. Never mind. Still none.

Bad luck, I suppose. The luck of the draw doesn't appear to favor you. I've gathered 80 thus far (though a few have been 100% blanked B3_P1's, so I turn those around to get them out of the way), and still have more room in the cache before hitting the hard limit of 100.

A good chunk of the work I've gotten so far has been rather heavily blanked, as well, so instead of ~10 hours for each task, they're ranging from 1.5-5 hours instead.

Not luck. I get one or two a month and have since last fall. I don't know what it is but it's not random.

It's why I shifted focus to other projects and lost a lot of interest in BOINC in general.

Why do AP tasks have a higher priority than Seti tasks?
I suspended all tasks and re-enabled them.It paused all setiathome tasks, that were running and started ap tasks instead.

Nothing went "high priority".

So,what happened to the FIFO structure? I thought, it runs task in order they were received.That is definitively not the case.The shortest deadline is still 12 days away.
Does anyone know, what the rules are to decide, what task to run next?