I have a situation where the internet is available for one hour a day to upload and download WUs. It seems to work only for heavy cpu usage WUs. Non-CPU intensive WUs are not considered when local preferences are set to maintain 1 days work load and an extra .1 workload. Only one NON-CPU intensive WU is downloaded. IS this normal? A lot of work is not accomplished this way.

What is looks like that only one NON-Cpu intensive WUs per project is allowed at a time regardless of network availability.

There's no use to have a cache of Non-CPU-intensive tasks. They're not really tasks in the sense of CPU-intensive tasks, where they actually contain data. They're usually used to do some kind of sustained measurement, over a period of time, such as Host or Network measurements, Web crawling or Network data access.

So it's normal to only have 1 NCI task, despite having a request for 1.1 days of work and 128 CPU cores available.

Edit: And as I had forgotten that you only use the network for 1 hour a day, it's probably useless to use the NCI task on your system. ;-)

---

It rather depends what the non-CPU intensive applications are supposed to do. The one I know best is QCN (Quake Catcher Network). It's supposed to do nothing much most of the time, until an earthquake happens: then, it's supposed to pass on details as quickly as possible so that the epicentre can be calculated and appropriate warnings issued.

There's not a great deal of value in running that application, if lack of network access prevents the warning being issued for up to 23 hours. Considerations like that may have influenced the designers of BOINC.

What is the work that would be accomplished (non-intensively) if the app in question was allowed to run continuously without network access?