Hi,

I had a situation some years ago when I wanted to limit the number of Milkyway@home tasks downloaded into my computer, because I had that computer on quite randomly. Just did not want to download too much tasks in reserve which would run over deadline if the computer was not on for days. Now I have the computer turned on for much longer periods. I just noticed that I get a single Milkyway@Home unit downloaded after the previous unit is reported. I really would like to get something like 30 units per download. I have following setup:

Windows 10 Pro (version 2004 / 19041.450)
BONC 7.15.7 (x64)

Project weight:
LHC@Home 100
Milkyway@Home 100
rosetta@home 200
World Community Grid 200

Current local rules for calculation in use:
Store at least 1 day worth of work
Store additionally 0.5 days worth of work

GPU workunits of Milkyway@home Separation 1.46 (opencl_nvidia_101)

I am quite sure that I just fiddled with the project weight and workunit storage settings to get less Milkyway@home project's workunits downloaded in the past. I wonder why it does not give me more workunits now when I loosened up those setttings. I had previously "at least 0,2" and additionally "0.2".

I had my GUI configured to show only packets under processing :). I switched to show all packets. Everything i ok.

There are 5 possible reasons I can think of straight off :-

1. You've been having a lot of errors recently and you're on parole?

2. In the cc_config.xml file you've set fetch_minimal_work to 1 which tells the system to do exactly what you describe

3. In app_config.xml you've set max_concurrent or project_max_concurrent to 1. This wouldn't force one in one out but might cause the problem

4. In WCG there's a setting on the preferences page that allows you to say how many concurrent jobs you want - is there an equivalent for Milkyway?

5. Are you short on disc space and that's all that your disc parameters will allow?

Oops - that will teach me to read to the end of the thread before posting :-)