How to set the CPU Start Time

[Mark Rose]

Originally Posted by LaurV

Read the "undoc.txt" file which come with the distribution. Look inside for the "PauseWhileRunning" option, and use "*[n] during from_time-to_time" up to your convenience, where n is the number of workers to pause (all, if you don't use any n).

Edit: for your schedule passing over the midnight, you may need to split the time in two, like "PauseWhileRunning = * during 19:00-24:00 else * during 0:00-07:00", I am not sure about this, it may also work without split.

So I tested this function with the following two formats and neither worked:

PauseWhileRunning=* during 12:58-12:59
PauseWhileRunning=mprime during 12:58-12:59

[LaurV]

First observation is that the time is quite short, I don't think that P95 checks the "schedule" at every iteration, it will waste a lot of time. Most probably the schedule is checked every "n" iterations (wild ass guess, I didn't look in the source) this may depends on your "print on screen at x iterations" and/or "save on disk at y iterations" settings or not, George could clarify that. If the time is so short P95 may not have time to check, or to fully stop.

Second, the second line there is a ... paradox. The program itself (mprime) runs, as he checks for itself if it runs, then it pauses, because it runs, but if it pauses, then it not runs... etc. Or it can be interpreted as stop forever... (?) because it checks for itself, it runs, therefore it pauses, but if it pauses, it will never check again for itself if it runs...

Or... does it? hehe...

[Mark Rose]

Originally Posted by LaurV

First observation is that the time is quite short, I don't think that P95 checks the "schedule" at every iteration, it will waste a lot of time. Most probably the schedule is checked every "n" iterations (wild ass guess, I didn't look in the source) this may depends on your "print on screen at x iterations" and/or "save on disk at y iterations" settings or not, George could clarify that. If the time is so short P95 may not have time to check, or to fully stop.

Second, the second line there is a ... paradox. The program itself (mprime) runs, as he checks for itself if it runs, then it pauses, because it runs, but if it pauses, then it not runs... etc. Or it can be interpreted as stop forever... (?) because it checks for itself, it runs, therefore it pauses, but if it pauses, it will never check again for itself if it runs...

Or... does it? hehe...

The default checking time is 10 seconds.

I tried mprime after * didn't work.

[LaurV]

Oh, I just remember a past discussion on the forum, where somebody else said the same, and conclusion was that some spaces around the = sign must be present (!? after the equal?)