(archive)MISFIT

[kracker]

Originally Posted by swl551

U must agree to try breaking it, not just letting it run.

EDIT: if i shred it using my secure shredder to nothingness, does that count?

[swl551]

Originally Posted by kracker

EDIT: if i shred it using my secure shredder to nothingness, does that count?

as long As there are no unhandled exceptions or crashes the the test is a success!

[swl551]

Originally Posted by kladner

I did not see that string. I attached the log files so you can look them over.

Looks good!

[swl551]

Might help new folks get setup more easily.

[bcp19]

If you have machines running both DC and LL TF work, do you need 2 instances of MISFIT running or can 1 handle it?

[swl551]

Originally Posted by bcp19

If you have machines running both DC and LL TF work, do you need 2 instances of MISFIT running or can 1 handle it?

Your environment can be handled by one instance but there are limitations if you want to keep the type of work segregated by instances. (to prevent cross pollination of work)

**With two physical machines just run MISFIT on each machine and cross pollination won't be an issue at all.**

**With one physical machine running two mfaktX instances then you will have to do work fetching and adding of work manually and directly into the desired WorkToDo.txt files.** (this can be done by the CLI Gpu72WorkFetcher.exe utility using different configuration files and executing via Windows Scheduler (or whatever))

If cross pollination of work is not an issue then there are no restrictions on MISFIT's implementation.

Feel free to clarify any restrictions/conditions you have in your environment that might produce a different option.

Also the Gpu72WorkFetcher.exe utility can use both the LLTF and the DCTF urls so you can fetch either type of work.

Thanks

[swl551]

Finally.... the long awaited......Version 2.4.0


1. Full integration of GPU72 Work Fetching including Fallback feature.
If fallback is configured and GPU72 responds to your work request with:
***No assignments available which match your criteria.**
MISFIT will override your configured settings with defaults and re-request work. This is to ENSURE you never run out of work.


2. Moved GIMPS work fetch out of GIOM and directly into main MISFIT functions. Much cleaner implementation and now GIMPS and GPU72 fetching follow identical IO and transformation functions.


3. Added a Work Calculator to the Work Fetch Menu. Designed to help you configure MISFIT so you don't run out of work!

4. Added a FORCE work balance menu item that will execute a full re-balance regardless of if needed. The benefit is that the duplicate exponent tosser is also forced to run. Mostly a diagnostic type of feature.

5. Directory GIOM_LOGS deprecated, but not removed, and is replaced with WEB_LOGS


6. Changed the determination of when to fetch work from the number of rows in MISFITworkToDo.txt to the calculation of GhDz remaining in said file. This provides a much better method for calibrating the balance between work consumption and work fetching. This should help you in determining if you are fetching work in suitable quantities to have a several day reserve. [hint hint, several day reserve!] Use the Work Calculator to assist in finding the right configuration settings.


7. Added file-locking to all I/O scenarios where MISFITworkToDo.txt is involved. A few conditions didn't have locking and that was OK when it was only possible to load the MISFITworkToDo.txt via the UI. Now with randomly timed fetching threads adding work to the file it was at risk of an un-handled IO collision.


8.Added LLDC stats to the Leaderboard

9. Added option to email Global Work Stats prior to Auto Results Uploading
MISFIT Global Work Status Report
****** REMAINING WORK INFORMATION ******
GhDzToDo:2,138.949
ExpRows:119
StgdRows:72
StgdGhDz:554.715
****** COMPLETED WORK INFORMATION ******
GhDzDone:346.121
ExpsDone:83
FactorsFound:1
ResultBytes:6403

10. Improved the the usage of the Remote Control Panel.


11. An improvement to the encryption key generation was done which will make MISFIT unable to decrypt your existing version 2.3.x SMTP, GIMPS passwords. Once re-encrypted with 2.4.x you cannot go back to 2.3.x without reconfiguration. Backup your MISFITconfig.txt if you before running 2.4.x.

12. Cleaned up Operations menu by removing items that already have buttons on the main form.

MANY thanks to
Flashjh
Kladner
Kracker
JMLMX
and of course Mr. GPU72 himself Chalsall


GET FROM http://mersenneforum.org/misfit/

[chalsall]

Thanks Scott.

This has come a very long way very quickly, and is filling a needed void.

Very nice work!

[kracker]

One BIG thing I did not notice and only noticed when it was uploading results:
I can't select from LL or DC TF work in GPU72.

Other than that.... wow thanks. misfit has reduced manual work so much... I haven't assigned or managed my "sessions" manually for weeks, MISFIT is doing it all!

[swl551]

Originally Posted by kracker

One BIG thing I did not notice and only noticed when it was uploading results:
I can't select from LL or DC TF work in GPU72.

Other than that.... wow thanks. misfit has reduced manual work so much... I haven't assigned or managed my "sessions" manually for weeks, MISFIT is doing it all!

Future addition.

As a work around you can configure the external fetcher to point to the DCTF url and within MISFIT switch the source to GPU72 when fetching TF, or EXTERNAL when fetching DCTF.

[kracker]

Originally Posted by swl551

Future addition.

As a work around you can configure the external fetcher to point to the DCTF url and within MISFIT switch the source to GPU72 when fetching TF, or EXTERNAL when fetching DCTF.

Ok, thanks