(archive)MISFIT - Page 13

swl551 · 2012-12-28, 19:33

In version 2.3.x the focus is on preventing IO with GIMPS during peak times. I have defined peak time (in my code) as 5 mins before the hour to 10 mins after the hour.

During this restricted window anything done via button clicks will get a dialog error indicating cannot perform task during peak time.

For automation it is more complicated.
Schedule exports/uploads can no longer be scheduled during that time frame. Existing schedule will be challenged during startup and you'd have to reschedule.

Time interval based exports/uploads will auto delay to past the restricted window if the event occurs within the restricted window.. this will cause the timer to drift past the window and future uploads won't fall in the window at all.

GIOM retries (if GIMPS is down) will also auto delay to past the restricted window if the event occurs within the restricted window. So if you have a schedule upload at 3:30 and it fails due to some primenet problem it retries every 30 mins. this puts the next retry right at peak time (4:00). In this case GIOM will delay that retry to after peak time.

In all automation scenarios the delay past peak time is randomized between 0 and 5 minutes. This delay is to prevent the thousands of MISFIT instances from uploading results at the same time after the peak window has passed.

So is everyone OK with this?

screenshot shows interval based upload occuring at peak time and then being delayed.

flashjh · 2012-12-29, 06:25

Quote:

Originally Posted by swl551

So is everyone OK with this?

Works for me.

axn · 2012-12-29, 15:28

Quote:

Originally Posted by swl551

I have defined peak time (in my code) as 5 mins before the hour to 10 mins after the hour.

How does the program determine this? Does it use local time, server time or perhaps a standard timezone like UTC? I ask this because not all time zones are an integral multiple away from UTC.

kracker · 2012-12-29, 15:57

Quote:

Originally Posted by axn

How does the program determine this? Does it use local time, server time or perhaps a standard timezone like UTC? I ask this because not all time zones are an integral multiple away from UTC.

I think UTC, but I am not sure.

swl551 · 2012-12-29, 16:10

Quote:

Originally Posted by axn

How does the program determine this? Does it use local time, server time or perhaps a standard timezone like UTC? I ask this because not all time zones are an integral multiple away from UTC.

Good point! I was just using PC's local time, but now will convert it to UTC.

swl551 · 2012-12-29, 17:35

Changed peak time definition to

2 mins before to 10 mins after the hour (UTC).

swl551 · 2013-01-03, 02:41

Suggestion from flashjh... Screenshot highlights the concept. Open for comments.

flashjh · 2013-01-03, 02:44

Quote:

Originally Posted by swl551

Suggestion from flashjh... Screenshot highlights the concept. Open for comments.

Looks good, but I don't know about the 'assing-out' during event ;)

swl551 · 2013-01-03, 02:45

Quote:

Originally Posted by flashjh

Looks good, but I don't know about the 'assing-out' during event ;)

Time for new glasses!

flashjh · 2013-01-03, 02:48

Quote:

Originally Posted by swl551

Time for new glasses!

I see you had deleted the picture when I posted that, if I had waited just a few minutes, I wouldn't have ever seen it

kracker · 2013-01-03, 03:18

Goddamnit. I wanted to see that!

2012-12-28, 19:33	#133
swl551 Aug 2012 New Hampshire 2³×101 Posts	2.3.x feature... discussion In version 2.3.x the focus is on preventing IO with GIMPS during peak times. I have defined peak time (in my code) as 5 mins before the hour to 10 mins after the hour. During this restricted window anything done via button clicks will get a dialog error indicating cannot perform task during peak time. For automation it is more complicated. Schedule exports/uploads can no longer be scheduled during that time frame. Existing schedule will be challenged during startup and you'd have to reschedule. Time interval based exports/uploads will auto delay to past the restricted window if the event occurs within the restricted window.. this will cause the timer to drift past the window and future uploads won't fall in the window at all. GIOM retries (if GIMPS is down) will also auto delay to past the restricted window if the event occurs within the restricted window. So if you have a schedule upload at 3:30 and it fails due to some primenet problem it retries every 30 mins. this puts the next retry right at peak time (4:00). In this case GIOM will delay that retry to after peak time. In all automation scenarios the delay past peak time is randomized between 0 and 5 minutes. This delay is to prevent the thousands of MISFIT instances from uploading results at the same time after the peak window has passed. So is everyone OK with this? screenshot shows interval based upload occuring at peak time and then being delayed. Attached Thumbnails Last fiddled with by swl551 on 2012-12-28 at 19:43

2012-12-29, 17:35	#138
swl551 Aug 2012 New Hampshire 2³·101 Posts	2.3.0 beta-1 is out there. Changed peak time definition to 2 mins before to 10 mins after the hour (UTC). Last fiddled with by swl551 on 2012-12-29 at 17:54

2013-01-03, 02:41	#139
swl551 Aug 2012 New Hampshire 328₁₆ Posts	Auto-Assigning work from MISFITworkToDo Suggestion from flashjh... Screenshot highlights the concept. Open for comments. Attached Thumbnails Last fiddled with by swl551 on 2013-01-03 at 02:52

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-01-03, 03:18	#143
kracker "Mr. Meeseeks" Jan 2012 California, USA 2³·271 Posts	Goddamnit. I wanted to see that!