I have created this thread because there is a lot of discussion around these tasks in the Panic Mode On (98) Server Problems? thread on pages 11 and 12. Don't get me wrong I think it is good to discuss how many tasks are getting. I just feel it is the wrong place to be discussing it. I personally find it not helpful when people say they get 100+ task and I do not receive any. My personal belief is that the server problem thread should be related just to that. People do not agree with me on this which I can kind of understand.

I feel it will be probably a week or more before we receive more tasks as there are 536 channels to complete before more data will be added. Of course I am hoping there will be more sooner rather than later

since AP came back ONE of my computers has been getting "waiting for GPU memory" ONLY on the AP WUs. The MB WUs run just fine. I "reset" the project and limited it to AP WU's and I still get the same message even though nothing is running on the GPU (according to GPU-Z).

367 in progress now but was around 440 AP's but there getting crunched :-)

Kitties got 648 left, and crunching them like crazy...LOL.
RAC has had a boost. And I still got one cruncher with no GPUs running."The secret o' life is enjoying the passage of time." 1977, James Taylor
"With cats." 2018, kittyman

GTX980, all AP's gone since many hours. CPU, a few tasks left, Intel HD4600 haven't started on its 41 AP's yet, had many MB tasks to do first.

Q8200/ATI 4850, will stay happy for 10-11 days.

Celeron M Lappie will stay happy for 10 days.

In short: I want more :-) (as usual)Too much hormone treated meat.
Too much Monsanto veggies.
Too old and outdated constitution.
A crazy problem, as you Yanks use to say......There is no God, and God never existed.

Has anybody that has had only these tasks selected not been sent any? I have not received any for a long time. I am thinking this could be because I am based in New Zealand & do not have my computer running 24 7.

No one knows for sure. You could do your own experiments. Me, 2 machines do CPU and GPU work, 2 machines do GPU only.

When I had it set for APs only, I would get a few on the CPU and GPU machines. None on the GPU only machines. When I allowed both MB and AP work, the machines with CPU and GPU work got 5 x the amount of APs than the GPU only machines.

But that doesn't mean anything. Last time we had any good amount of APs, both of these machines didn't get any APs. If anything, my oldest machines got more work than my newest machines.

So there doesn't seem to be any rhyme or reason. Your ideas are as good as mine

Aside from potential bugs/flaws, there are naturally chaotic elements in the task scheduling that are more or less unmanaged. That means that, over many hosts, every possibility of normal and weird states will emerge eventually.

[Edit:] Ever run that old life simulation, whereby a few simple rules lead to pretty organic looking behaviour ? similar deal."Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Generally.. as I mentioned a week or so ago in the Panic thread.. if you have an empty cache and you are requesting a very large amount of work, the scheduler tends to not send you anything at all, unless there is a lot of work available. Like.. if there's only one or two tapes being split and the creation rate is less than 0.5/sec and you're requesting 2.5M seconds of work on an empty cache.. you won't get anything at all. If you drop your cache settings down so that you're only asking for ~200k seconds.. you'll start getting some tasks.

But.. if there are 3+ tapes and the creation rate is 1+/sec, requesting 2.5M seconds on an empty cache fetches pretty decent hauls. Once you start getting some work in your cache, it seems to fill up more reliably and faster.

Something I have no experience with, but I've read off and on from some of the regular posters around here is when it comes to GPUs, CPU requests tend to be filled first, leaving the GPU bored and idle until the CPU cache is filled, and then generally, you end up with having to make 20+ requests to get 20-30 APs for the GPUs because the server just.. doesn't seem to want to send anything to GPUs without a little bit of a fight. Again, on that one, I think once you get a small pile in the cache, they tend to start flowing in a bit smoother.

Those are just my observations, your results will vary.Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I don't see that. When downloading APs (only), my GPUs fill first and it's a struggle to get any CPU APs. Generally the CPU will not get any APs unless there is no work going through the CPU. Once the CPU is basically idle, the only way to get CPU APs is to hit the update button in the last 3 seconds, and I only get 1-2 (generally) at a time... makes for a long time to fill a CPU cache.