Did not know there was a newest (and stable) version of the WCG client, so what is that exact version, as knreed sure will be interested to learn of the non-replacement of the previous 6.10 release [which exactly... was it 6.10.58?].

Been testing the WCG builds and discussing offline with techs, now a work fetch issue popping up too, a fix just checked in by devs.

Basics is, that the buffer is sized in-amongst to the hours a device is on and connected in say last 10 days. These values are stored in the below 5 [sample] fraction values, in the client_state.xml:

<on_frac>0.938831</on_frac>
<connected_frac>0.979211</connected_frac>
<cpu_and_network_available_frac>0.978738</cpu_and_network_available_frac>
<active_frac>0.999512</active_frac>
<gpu_active_frac>0.999512</gpu_active_frac>

This says essentially that this host is on 93% and when on, virtually computes 100%. Work is buffered on that basis.

There's actually more issues, such as slow adjusting of projected runtimes. E.g. I want 2 days, but to get that I have to set the cache to 3 days [because my host is much much faster than FLOPS in the WU headers suggest it will take]. My message is; play with the cache values to get what you want [till we really have a Long Term Support] release, which is as I understand it, for many 7.0.xx, but could also be fast-tracked to become 7.2.xx and that does not even exist yet, except in a feature complete alpha alpha 7.1.15 build.