I really don't think this has anything to do with when the records may or may not be saved to archive, rather it has to do with the timestamps of the records (there is a difference). A system under load may save records at (slightly) different times but the system should still timestamp archive records in a consistent manner.
Little point in further supposition until we have config and log info. Gary On Saturday, 4 January 2020 08:16:20 UTC+10, Pat wrote: > > I agree that Belchertown skin has a lot going on with it, but that > shouldn't delay weewx from saving the archive since the skin runs after the > archive is run. > > The only scenario I can think of where the skin would slow things down is > if the skin is running longer than 300s to generate the graph json files, > which is causing weewx to delay on the next archive interval. > > This was common on a Pi Zero in early versions of the skin (I haven't seen > it being reported in the last ~12 months though since updating the chart > json generator) > > > > On Friday, January 3, 2020 at 4:10:18 PM UTC-5, vince wrote: >> >> On Friday, January 3, 2020 at 12:41:08 PM UTC-8, Pat wrote: >>> >>> Side note: I'm a little lost on this one. Not sure why weewx isn't >>> saving records consistently every 300s. (Nothing to do with the skin). >>> Maybe something to do with the resources of the Pi being stretched thin? >>> >> >>> >> >> What model pi is it ? >> What other than weewx is running on it ? >> >> I'll have to check my tiny/weak Seagate Dockstar at home, but my >> recollection is that weewx not saving exactly on a 300s interval is not >> that unusual. Sometimes the skins take longer than at other times to >> process as well. Belchertown is a rather intensive skin to run from what >> I've seen. My recollection is the processing time for that one can be >> rather high compared with more minimal skins. >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/5f393de6-00d9-4351-8fc7-4237c2ca8f4e%40googlegroups.com.
