Enigma, I believe, has only produced a "no-pie" app, which does only work on earlier ARM/Android. It's not marked/named as such, though.

Recent work request received 'no work available' response --> disallowed

The last line is the killer, and 'recent' can be up to 24 hours ago.

It might be helpful if you could post one single, complete [work_fetch_debug] log cycle from your machine, and we could work through it together, project by project, and work out why BOINC didn't request work until it reached NFS.

So is there a bug if the project's prio is about 2 to 3 orders of magnitude greater (abs()) than it should be? NFS prio should be down around -2.63 to -0.263 as it's already at 45% of maximum potential RAC while MindModeling reports -1.9 prio and is at 3-7% of potential RAC from days on end of no work. How does the NFS REC get such a high magnitude prio of -263 as it's credit payout is NOT 150 times greater than MindModeling? The expected credit per WU is about 3x greater as is the expected RAC over MindmModeling on this particular machine.

Prio is not abs()

- it's straight maths. The highest possible priority is zero, everything negative is lower. And -263.383 is very much lower indeed.

If MindModeling rarely has work, the chances of hitting it with a random fetch are very low. So most requests will get a response of 'no work available', and will trigger one of the many backoffs -

2/23/2016 5:31:37 PM |  | [work_fetch] No project chosen for work fetch
2/23/2016 5:31:39 PM |  | [work_fetch] Request work fetch: Backoff ended for MindModeling@Beta

The log message "not highest priority" comes from your local client, not from the server. It didn't even ask the server for work - so it won't get any reply relating to work availability.

2/17/2016 2:09:38 PM | MindModeling@Beta | Not requesting tasks: don't need (CPU: not highest priority project; NVIDIA GPU: )

2/22/2016 11:37:55 AM | MindModeling@Beta | [work_fetch] share 0.324
.
.
.
2/22/2016 11:37:55 AM | NFS@Home | [work_fetch] share 0.001

2/22/2016 11:37:55 AM | MindModeling@Beta | [work_fetch] REC 3509.462 prio -1.989 can request work
.
.
.
2/22/2016 11:37:55 AM | NFS@Home | [work_fetch] REC 1949.634 prio -263.383 can request work

2/17/2016 2:09:38 PM | MindModeling@Beta | [work_fetch] share 0.519

2/17/2016 2:11:01 PM | MindModeling@Beta | [work_fetch] share 0.000 no applications

2/17/2016 2:09:38 PM | MindModeling@Beta | Not requesting tasks: don't need (CPU: not highest priority project; NVIDIA GPU: )

2/17/2016 2:20:09 PM | MindModeling@Beta | Project has no tasks available

What's the debt formula? Is it based on RAC or total credit? Credit granted per project is wildly different and not useful in inter-project debt calculations.

It's based on RAC.

No, it's based on REC (Recent Estimated Credit) - project inflation is excluded.

Estimated Credit

That paper suggests a delay rate (half life) for REC of 1 month: in the end, a default of 10 days was chosen, but that's configurable.

Still no change after 2 days.

Fellow BOINCers,

Is there a manner by which one configure Boinc Manager to say "Do not accept tasks from project xyz where the disk space required for that particular task exceeds X GB or MB)"?

Stuart

Even with the present form of the scheduler, BOINC still uses a form of debt between projects.

(you'll likely have to create the file)

The BOINC v7.6.xx range (you'll be wanting to use v7.6.22 now) have a handy 'Event log options...' picker under the Options menu, or Ctrl-Shift-F.

If you change something there, BOINC will write out a complete cc_config.xml file, nicely formatted, with everything in alphabetical order, and pre-populated with default values. It's much easier, and safer from typos, to start from that.

I'll try installing the 7.6.22 version later and see if the issue continues but was curious how BOINCMGR.EXE decides on the amount of vram to reserve.

Are you sure? I think you have misread the units that resource monitor is listing. They are in K = 1000 bytes, not M = 1,000,000 bytes. Your figures then are close to my Win 7 machine.

First things first, terminology: VRAM == memory on a videocard, fully called Video RAM, hence abbreviated to VRAM. If you need to abbreviate virtual memory, it's VM. Yes, the same as Virtual Machine.

Second, where do you look for the virtual memory usage of BOINC Manager? I just checked if it's a column option in Windows Task Manager or in Resource Monitor, but neither has the option. Unless it's named differently.

I even tried to set up a Performance Monitor for it, but haven't found a correct option yet. So what do you use?

Also, is this bog standard BOINC Manager, or did you set for instance to use unlimited Event Log through cc_config.xml?

<cc_config>
   <log_flags>
   </log_flags>
   <options>
       <allow_multiple_clients>1</allow_multiple_clients> - allows you to split into 2 or more clients.
       <fetch_minimal_work>1</fetch_minimal_work> - tells the client to fetch only 1 WU at a time and can stop some projects flooding the buffer while your client waits on a high resource project to get some work ready.
       <ncpus>X</ncpus> - where X is the number of cores per client you split into.  Actually, setting this higher than the cores in your machine has benefits.
       <fetch_on_update>1</fetch_on_update> - this causes projects that wouldn't normally get work because of the work-fetch algorithm decisions to fetch some WU's and goes well with <fetch_minimal_work>1</fetch_minimal_work>.

These keep your many machines running BOINC from flooding your single internet connection:
      <report_results_immediately>1</report_results_immediately>
      <max_file_xfers>2</max_file_xfers>

The rest of these are just some nice options.
      <skip_cpu_benchmarks>1</skip_cpu_benchmarks> - machines exclusively running BOINC 99.9% of the time don't need to be BMed.
      <start_delay>15</start_delay> - give you a chance to stop BOINC before apps start if you've made a mistake in configuration.
      <suppress_net_info>1</suppress_net_info> - doesn't report your IP.
     
    </options>
</cc_config>