That's good to know jgoldsti.... only complaint i have with the 5.7.4 alpha is that the snooze only held for about 15 seconds and some strange suspending of a HDC WU in progress, starting the next HDC, but resuming it when the second was finished...... the hobby department may support and BOiNC developers forum.

thanks

It used to be indefinite, but have read of the alpha's coming out of snooze, so guess it will be fixed in the upcoming, or maybe it already has in 5.7.5.

Edit: went to check and the snooze is broke. Set Work to Always, Suspend works. I had it on 'work per schedule'. Per the uBW, it was supposed to be 1 hour.

There are some new options in the alpha's (the pref files) that allow u to qualify how much ram to use when working and how much when 'idle'.... work is 50%, idle is 90%. That may explain why an extra large suspended (it was a monster), then finished middle of the night, when all apps were unloaded.

<ram_max_used_busy_pct>50.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90.000000</ram_max_used_idle_pct>

It's only because they are in my override file, copied from the dev site that i got ahold of this.

it's 1 minute ;>) and it was confirmed as still to be fixed in post 5.7.5. Per the UBW it's 1 hour if using work scheduling... unlimited if set to work all time?

retsof,

In past, it would just finish WU's within a project sequentially for WCG. They had identical due dates.... had it several times now before increasing the 'work' ram limit to 60%. See if it happens again.

I'd yet to see a single project switch WU's, but that's what it's been doing, with a 'wait for memory' in the message log. I've not experimented if this is in anyway related to the 'keep in memory' option, when one e.g. elects to switch projects every X hours like WCG and Rosetta. That option with the much optimised checkpoint related switching minimizes crunch time loss substantially. Thought thought that all improvements was functioning only with 5.7.x and up.

cheers