[QUOTE=flashjh;334662]Now you can see why I needed it so badly for 7 GPUs :smile:

Edit: Any way you can make MISFIT cook breakfast for me? ;)[/QUOTE]
Flashjh. I failed to get MISFIT to cook breakfast with any consistency, but I did discover that a GPU cooling fan can whisk up a nice [I]vanilla custard sauce [/I]as good as any French chef.

Try it!

[OT][QUOTE=swl551;335278]Flashjh. I failed to get MISFIT to cook breakfast with any consistency, but I did discover that a GPU cooling fan can whisk up a nice [I]vanilla custard sauce [/I]as good as any French chef.

Try it![/QUOTE]

With all the heat from my GPUs and the cooling fans, we could cook pancakes and scrambled eggs with a vanilla custard sauce topping for breakfast.[/OT]

[QUOTE=flashjh;335291][OT]

With all the heat from my GPUs and the cooling fans, we could cook pancakes and scrambled eggs with a vanilla custard sauce topping for breakfast.[/OT][/QUOTE]

You could try preheating food like a microwave on top. :devil:

Work balance question
 

If there are 6 lines remaining in one worktodo file, 1 in another, and "Balance when difference >" is set to 10, will the smaller file run out of work and the instance stop?

Or is there some sort of safety valve to ensure that none of the files can run out?

I am seeing this situation since I manually added a bunch of short double checks; normally this would not have happened.

[QUOTE=Chuck;336239]If there are 6 lines remaining in one worktodo file, 1 in another, and "Balance when difference >" is set to 10, will the smaller file run out of work and the instance stop?

Or is there some sort of safety valve to ensure that none of the files can run out?

I am seeing this situation since I manually added a bunch of short double checks; normally this would not have happened.[/QUOTE]
Chuck your conclusion is correct: No such fail-safe exists. It is a good idea though.

Also, with a very slow card (GTX 440) and long assignments (to 74 bits), with MISFIT set to minimum GHz-D/D settings, it normally has two exponents in the work to do file and two exponents in the staging file.

Usually this works fine, but sometimes mfaktc runs out of the exponents in the work to do and quits. MISFIT thinks that mfaktc stalled, and all work stops even though there are still exponents in the staging file.

[QUOTE=TObject;336288]Also, with a very slow card (GTX 440) and long assignments (to 74 bits), with MISFIT set to minimum GHz-D/D settings, it normally has two exponents in the work to do file and two exponents in the staging file.

Usually this works fine, but sometimes mfaktc runs out of the exponents in the work to do and quits. MISFIT thinks that mfaktc stalled, and all work stops even though there are still exponents in the staging file.[/QUOTE]

That is why I have stated a best practice of keeping at least two days of work on hand. One days worth in your live workToDos and one days worth in your reserve. Given a proper seeding the auto-fetching and draining system works fine.

[QUOTE=swl551;336294]That is why I have stated a best practice of keeping at least two days of work on hand. One days worth in your live workToDos and one days worth in your reserve. Given a proper seeding the auto-fetching and draining system works fine.[/QUOTE]

Four exponents to 74, at the current TF front, is well over two days of work for non-overclocked GTX 440.

[QUOTE=Chuck;336239]If there are 6 lines remaining in one worktodo file, 1 in another, and "Balance when difference >" is set to 10, will the smaller file run out of work and the instance stop?

Or is there some sort of safety valve to ensure that none of the files can run out?

I am seeing this situation since I manually added a bunch of short double checks; normally this would not have happened.[/QUOTE]


Maybe the minimum 'balance when difference >' setting should be a function of the number (in units or ghzd) fetched, so that one can't really fetch less than one can balance.

[QUOTE=Aramis Wyler;336296]Maybe the minimum 'balance when difference >' setting should be a function of the number (in units or ghzd) fetched, so that one can't really fetch less than one can balance.[/QUOTE]

I don't understand your proposal. One row in a file is one assignment. I cannot move part of that row.

Also I'm still not seeing a problem that cannot be resolved by modifying configuration to address the situation. Don't want work to run out, put 10 days of work in your queue. It won't hurt anyone. There is enough work to go around.

[QUOTE=swl551;336300]Also I'm still not seeing a problem that cannot be resolved by modifying configuration to address the situation. Don't want work to run out, put 10 days of work in your queue. It won't hurt anyone. There is enough work to go around.[/QUOTE]

Sure... But can be argued this is sub-optimal. And requires a human in the loop.

If MISFIT has knowledge about how many GHzDays/day an instance can do, then it should be able to balance the worktodo.txt files such that each instance has a reasonable amount of work based on that.