worktodo.add
 

Ok, now that mfaktC and mfaktO both support worktodo.add I can make a configuration option in MISFIT to push work into that file instead of loading directly into workToDo.txt.

Comments please!

[QUOTE=swl551;396736]Comments please![/QUOTE]

Yes!!! No more race conditions!!! :smile:

[QUOTE=swl551;396736]Ok, now that mfaktC and mfaktO both support worktodo.add I can make a configuration option in MISFIT to push work into that file instead of loading directly into workToDo.txt.

Comments please![/QUOTE]
+1

Sounds good.

VERSION 2.10.0
 

VERSION 2.10.0
1. Added a new report showing all "Recent Results Uploads" **special feature for TheMawn**
2. Added configuration to push work assignments into WorkToDo.add instead of WorkToDo.txt (off by default)
**please verify your version of MFAKTx supports .ADD**

[B]See the changelog for important notations on the .ADD feature[/B]



[url]http://www.mersenneforum.org/misfit/downloads/MISFIT/[/url]

So does Misfit take into account worktodo.add when calculating how much work is remaining?


[QUOTE=swl551;396844]VERSION 2.10.0
1. Added a new report showing all "Recent Results Uploads" **special feature for TheMawn**
[/QUOTE]

:smile:

:TheMawn:

[QUOTE=TheMawn;396847]So does Misfit take into account worktodo.add when calculating how much work is remaining?

[/QUOTE]

No, because worktodo.add is just a temporary/gateway file into workToDo.txt


If the WorkToDo.txt files are running low MISFIT will create a .ADD file with the desired amount of work and within minutes MFAKTx will absorb that work into the WorkToDo.txt file.

I hope that helps.

Okay, sounds good. Actually I just mis-calculated the way MISFIT adds work. It used to dump it straight to worktodo.txt, now it dumps to worktodo.add instead, if the option is checked. Much simpler than I made it out to be.

Thanks

I'll probably regret asking this....
 

What was/is the reasoning for 2 and now 3 (or 4) worktodo files?

On my setup I have a mfaktc worktodo.txt and a misfit worktodo.txt.
I don't understand why misfit couldn't add new work directly into the mfaktc worktodo.txt.

And now I'm even more confused why there is now a misfit worktodo.add.

I can see where a mfaktc worktodo.add could be used for work I manually add outside of misfit.

Maybe if I knew what a "race condition" was ...

[QUOTE=petrw1;396898]On my setup I have a mfaktc worktodo.txt and a misfit worktodo.txt.[/QUOTE]
This makes more sense when MISFIT is managing multiple mfaktc instances: MISFIT gets work and puts it in its own worktodo.txt file. As the instances need additional work, it is doled out from MISFIT's file.
[QUOTE=petrw1;396898]Maybe if I knew what a "race condition" was ...[/QUOTE]
When two processes try to read or write the same file at the same time, confusing things can happen. [url]https://en.wikipedia.org/wiki/Race_condition[/url]

[QUOTE=petrw1;396898]What was/is the reasoning for 2 and now 3 (or 4) worktodo files?

On my setup I have a mfaktc worktodo.txt and a misfit worktodo.txt.
I don't understand why misfit couldn't add new work directly into the mfaktc worktodo.txt.

And now I'm even more confused why there is now a misfit worktodo.add.

I can see where a mfaktc worktodo.add could be used for work I manually add outside of misfit.

Maybe if I knew what a "race condition" was ...[/QUOTE]

Before mfaktc could do sieving on the GPU it required the CPU and maximum throughput was achieved running 4 instances. In his GPU farm FlashJH ran around 40 instances and misfit managed it all. Nowadays most people just have 1 instance.

The .add file is not a misfit file, it is mfaktc that wants this file as a controlled path to deliver work into workto do.txt files