It is not currently possible to dynamically distribute the WUs into smaller sizes. Each WU is from a specific trajectory - the Project, Run and Clone numbers - run for so many steps from the starting point of that trajectory. The Gen 0 WU starts from the beginning and when returned the next Gen 1 WU is created using the final status of Gen 0 as the starting. The same atoms will be in the simulation, so the size can't be changed there, and the final results for each PRC trajectory depend on piecing together Gen 0 through Gen n. That is easily done with a fixed number of steps, generating various different number of steps would require major changes to the software code and the analysis code used non the results.Trokari wrote:How about being able to dynamically distribute the required simulations into smaller packages? I don't know at all if it's possible to implement in FAH's case, tho. It would be nice if you could choose the WU size you prefer from the client's UI
and the work server would then be able to split the calculations into requested size and go from there.
There could be certain, fixed work unit sizes that folders would be able to choose from. This wouldn't cause problem with the WU time sensitivity either and actually it would probably improve on getting calculations finished in
time as fewer work units would go to waste due to expiration at least for intermittent folders like myself.
Something similar was tried some years ago. This was referred to as a "streaming core". It would assign work, when work was stopped results would be sent back and the WU be reassigned to someone else to continue from that point. They ran into a number of problems and eventually abandoned this approach.
There have been some other things done in the past to provide smaller assignments such as the NaCl one for Google Chrome or the one developed by Sony in collaboration with F@h for their Android phones. Both of those were active for a few years, but both ended when Google and Sony ended their support for the necessary technical items.
Going forward, F@h has limitations on just how much software can be developed. For years they had just a single full time developer, a second was recently hired to work on developing the next version of the client.
Now you did not provide any details on what you are running F@h on in either of your posts. With more detail we could make suggestions that may get you a more appropriate mix of WUs, with more being likely to finish in the time you are providing.