(archive)MISFIT - Page 52

LaurV · 2013-03-06, 18:20

Quote:

Originally Posted by swl551

Using WorkToDo as a component of the detection should resolve the issue.
Laurv: I'll have a release in a day or two for you to test.

Thanks. Related to using worktodo, you can use better the result file, which will change more often in size, or use both, as I commented before (I am thinking of the situation when worktodo does not change in size, only its first line changes, from "bla-bla,71,73" to "bla-bla,72,73", but the result file changes in size too, as a new line is added to it), beside of the method with checkpoints which is better for long assignments.

edit: and a bit of nitpicking: after a successful manual report, the "next upload" bar should go to zero (it makes no sense to report again after 5 minutes, if I got impatient and clicked the button just 5 minutes before the bar reached the end of the track...)

@Xyzzy: how about here, in "software"? yafu has it in factoring project, but misfit is not about factoring, is a software tool to help with mfaktc/o and cudalucas, so either here, or in gpu-whatever (just a suggestion, other idea welcomed too).

kracker · 2013-03-06, 19:14

Quote:

Originally Posted by LaurV

@Xyzzy: how about here, in "software"? yafu has it in factoring project, but misfit is not about factoring, is a software tool to help with mfaktc/o and cudalucas, so either here, or in gpu-whatever (just a suggestion, other idea welcomed too).

+1

swl551 · 2013-03-07, 02:05

Stalled Process detection now considers the LastWriteTime of the following
1. The latest checkpoint file (if any)
2. WorkToDo.txt
3. Results.txt

When all three stall out then the instance is declared stalled. The side effect of this is that work balancing, work adding/draining staged work and results uploading can temporarily mask the fact that a process is actually stalled. Therefore it is recommended you stick with the stalled detection defaults of
Minutes between checks=5;
Number of times files detected stalled=3;

See LaurV's mind blowing writeup and stunning graphic to understand the motivation for this change.

Although you probably didn't have the issue LaurV describes the code really needs to be tested by persons other than Laurv to ensure I did not break any existing functionality (hey that's why we beta test!)

Thanks

Scott

My formum FTP account is not allowing my login, so for now get from skydrive http://sdrv.ms/169QpcY

swl551 · 2013-03-07, 12:55

I removed the logic detecting changes to WorkToDo as part of the stalled detection process. WorkToDo can be changed by many of MISFIT's native functions which could mask an actual stalled process. On the other hand Results.txt is rarely touched by MISFIT and therefore is less likely to prolong the detection of a stalled process.

It is still recommended you stick with the stalled detection defaults of:
Minutes between checks=5;
Number of times files detected stalled=3;

Get from http://mersenneforum.org/misfit/

LaurV · 2013-03-07, 13:07

Tested beta1 for a while, used pause/break key to simulate a stall, which was properly detected and properly resumed when I un'stalled it. Let it run for about two hours, no false alarm. Deleted. "Da capo al fine" with beta2. I hope you don't do a beta3 in 35 minutes

swl551 · 2013-03-07, 13:11

Quote:

Originally Posted by LaurV

Tested beta1 for a while, used pause/break key to simulate a stall, which was properly detected and properly resumed when I un'stalled it. Let it run for about two hours, no false alarm. Deleted. "Da capo al fine" with beta2. I hope you don't do a beta3 in 35 minutes

No, I think we're done on this issue, unless someone reports bad things!

swl551 · 2013-03-07, 14:10

Quote:

Originally Posted by LaurV

Tested beta1 for a while, used pause/break key to simulate a stall, which was properly detected and properly resumed when I un'stalled it. Let it run for about two hours, no false alarm. Deleted. "Da capo al fine" with beta2. I hope you don't do a beta3 in 35 minutes

On another note: Has anyone mentioned your avatar photo is disturbing. Something about it makes me uneasy. I try to avoid looking at it...

kracker · 2013-03-07, 15:12

Quote:

Originally Posted by swl551

On another note: Has anyone mentioned your avatar photo is disturbing. Something about it makes me uneasy. I try to avoid looking at it...

That's. strange... Really?

swl551 · 2013-03-07, 15:28

Quote:

Originally Posted by kracker

That's. strange... Really?

Well if you find that photo soothing then mabye you are strange

I KNOW I AM NORMAL.

Chuck · 2013-03-07, 15:31

Great; I bumped my checkpoint frequency back up to 10 minutes. I was also having the false stall warnings when working the short-duration 332M exponents.

Chuck · 2013-03-07, 15:32

Quote:

Originally Posted by swl551

Well if you find that photo soothing then mabye you are strange

I KNOW I AM NORMAL.

It's probably because the "S" is reversed.

2013-03-07, 02:05	#564
swl551 Aug 2012 New Hampshire 2³×101 Posts	2.4.7 beta 1 Stalled Process detection now considers the LastWriteTime of the following 1. The latest checkpoint file (if any) 2. WorkToDo.txt 3. Results.txt When all three stall out then the instance is declared stalled. The side effect of this is that work balancing, work adding/draining staged work and results uploading can temporarily mask the fact that a process is actually stalled. Therefore it is recommended you stick with the stalled detection defaults of Minutes between checks=5; Number of times files detected stalled=3; See LaurV's mind blowing writeup and stunning graphic to understand the motivation for this change. Although you probably didn't have the issue LaurV describes the code really needs to be tested by persons other than Laurv to ensure I did not break any existing functionality (hey that's why we beta test!) Thanks Scott My formum FTP account is not allowing my login, so for now get from skydrive http://sdrv.ms/169QpcY Last fiddled with by swl551 on 2013-03-07 at 02:08

2013-03-07, 12:55	#565
swl551 Aug 2012 New Hampshire 2³×101 Posts	2.4.7 beta 2 I removed the logic detecting changes to WorkToDo as part of the stalled detection process. WorkToDo can be changed by many of MISFIT's native functions which could mask an actual stalled process. On the other hand Results.txt is rarely touched by MISFIT and therefore is less likely to prolong the detection of a stalled process. It is still recommended you stick with the stalled detection defaults of: Minutes between checks=5; Number of times files detected stalled=3; Get from http://mersenneforum.org/misfit/ Last fiddled with by swl551 on 2013-03-07 at 12:57

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
questions about misfit	jschwar313	MISFIT	1	2016-02-02 00:32
Help with Misfit	TheMawn	MISFIT	18	2015-06-21 22:00
Misfit feature request.	Aramis Wyler	MISFIT	15	2015-03-04 21:13
MISFIT 2.9	swl551	MISFIT	44	2014-12-15 12:46
MISFIT for MFAKTx	swl551	MISFIT	186	2014-02-05 23:27

2013-03-07, 13:07	#566
LaurV Romulan Interpreter Jun 2011 Thailand 9637₁₀ Posts	Tested beta1 for a while, used pause/break key to simulate a stall, which was properly detected and properly resumed when I un'stalled it. Let it run for about two hours, no false alarm. Deleted. "Da capo al fine" with beta2. I hope you don't do a beta3 in 35 minutes

2013-03-07, 15:31	#571
Chuck May 2011 Orange Park, FL 885₁₀ Posts	Great; I bumped my checkpoint frequency back up to 10 minutes. I was also having the false stall warnings when working the short-duration 332M exponents.