So over at YAFU some of the 32t WU's can go for 14 days.

The project developer, Yoyo, set up a dual deadline scenario.

The first deadline is the one the client shows and is the date by which the WU must be started.

The second deadline is the validation deadline which the WU needs to be completed by and is set at 7 days past the start deadline.

Not sure how YoYo implemented this but it's a great solution to this.

Looking through the long WU history I'm seeing 3 to 8 CPU days of wasted time on many WU's and a list of 5 to 15 attempts before the WU is completed.

What do you think?

(Personally, I like the long WU's and will do them all the time but aborting 300-500k second WU's tonight is making me nauseous.)

Forgot to add something.


If you make longs multi core by default (long1 = 8 core, long2= 4 core, long3 = 2 core) then limiting each client to 2 long1, 4 long 2 and 8 long3's would equally distribute the load and prevent the user aborts and management just before deadlines.

It might also encourage more to do longs.

Just another tactic seen at YAFU to deal with the 16 and 32 thread WU's. 2 per machine, maximum, ignoring the user default of 'unlimited'.