Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re: Efficiency of indoor grow light timer

by Anonymous Monk
on Nov 14, 2017 at 00:42 UTC ( #1203317=note: print w/replies, xml ) Need Help??

in reply to Efficiency of indoor grow light timer

You obviously do not need to check every fifteen seconds for an eventuality which you know will not occur for many hours hence.
  • Comment on Re: Efficiency of indoor grow light timer

Replies are listed 'Best First'.
Re^2: Efficiency of indoor grow light timer
by jdporter (Canon) on Nov 15, 2017 at 16:34 UTC

    Just because an answer is "obvious" doesn't mean it is correct.

    The frequency with which you check for the event depends only on how quickly you have to react to it when it does happen. If the SLA says that the system must respond with 15 seconds of the event happening, then you have to check for it at least that often. It doesn't matter whether it happens every 30 seconds or every 30 days.

    I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.
Re^2: Efficiency of indoor grow light timer
by stevieb (Canon) on Dec 12, 2017 at 00:19 UTC

    The status is checked at such periods is because a DB entry needs to be updated, so the front-end UI, driven by JS, represents the accurate status of the grow lamp being on or off. If something goes wrong, I can't just check every X hours; I need to know live-time whether things are ok or not. To further, the checks happen to ensure the sanity of the day, the time of day, and that the configuration is correct for the "season" for which we're growing in.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1203317]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (8)
As of 2020-02-25 13:38 GMT
Find Nodes?
    Voting Booth?
    What numbers are you going to focus on primarily in 2020?

    Results (110 votes). Check out past polls.