![]() |
|
|
#67 | |
|
Aug 2012
New Hampshire
14508 Posts |
Quote:
Try it! |
|
|
|
|
|
|
#68 |
|
"Jerry"
Nov 2011
Vancouver, WA
1,123 Posts |
[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]
Last fiddled with by flashjh on 2013-03-29 at 00:21 |
|
|
|
|
|
#69 |
|
"Mr. Meeseeks"
Jan 2012
California, USA
23·271 Posts |
|
|
|
|
|
|
#70 |
|
May 2011
Orange Park, FL
3×5×59 Posts |
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. |
|
|
|
|
|
#71 | |
|
Aug 2012
New Hampshire
23·101 Posts |
Quote:
|
|
|
|
|
|
|
#72 |
|
Feb 2012
6258 Posts |
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. |
|
|
|
|
|
#73 | |
|
Aug 2012
New Hampshire
23·101 Posts |
Quote:
|
|
|
|
|
|
|
#74 |
|
Feb 2012
34·5 Posts |
Four exponents to 74, at the current TF front, is well over two days of work for non-overclocked GTX 440.
Last fiddled with by TObject on 2013-04-06 at 20:05 |
|
|
|
|
|
#75 | |
|
"Bill Staffen"
Jan 2013
Pittsburgh, PA, USA
23·53 Posts |
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. |
|
|
|
|
|
|
#76 | |
|
Aug 2012
New Hampshire
23×101 Posts |
Quote:
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. |
|
|
|
|
|
|
#77 | |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
974710 Posts |
Quote:
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. |
|
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| released: MISFIT for MFAKTx version 2.11.0 (31-Jan-2017) | swl551 | MISFIT | 19 | 2020-11-18 14:29 |
| MISFIT 2.9 | swl551 | MISFIT | 44 | 2014-12-15 12:46 |
| MfaktX Controller (Windows) | Mini-Geek | Software | 52 | 2014-02-18 18:27 |
| MFAKTx speed menu (windows) | swl551 | Software | 8 | 2013-03-07 00:16 |
| (archive)mfaktXHelper - utility for managing mfaktX installations | swl551 | MISFIT | 57 | 2012-08-12 03:37 |