I have noticed that BOINC downloads new SETI tasks only after the previous task has been reported to the server which can take several minutes. Can this be changed? I could output maybe two times as much work as I do now if the client didn't idle for several minutes in-between tasks. I don't want to use the cache to solve this as I also run PrimeGrid where being first to report tasks is important and therefore cache should be set to zero. PrimeGrid is set up so that new tasks are downloaded when the previous is close to completion and there is no wasted time. I want this feature to SETI.

Unfortunately, your two requirements are incompatible. You want a cache for SETI, you want 'just in time' for PrimeGrid.

A cache of 0.01 day (~15 minutes) might suit you. Alternatively, it is technically possible to set up two independent instances of BOINC, with different cache settings on each - you need to be careful that they don't both try to use the same hardware at the same time. One instance for CPUs only, and the other for GPUs only, is a possibility.

Or just set Primegrid to a different venue/location than Seti. Then he can use the web-based cache settings, different for each project.

---