It's seeming like that's my best option - Move the NOAA reports to a 2nd skin, then add that skin to the install.py.
On Friday, August 24, 2018 at 7:11:01 PM UTC-4, gjr80 wrote: > > On Saturday, 25 August 2018 08:14:40 UTC+10, Pat wrote: >> >> >> I'm assuming if this is only affecting the highchartsDay class - and not >> the others - that there's a way to make the day charts play nice with the >> other SLEs? >> > > No, it will affect the others, week will be the same, month and year will > likely be the same though there could be some subtleties going on as the > period increases to match the SummaryBy period. > > Thinking some more you could check timespan.stop against the last good > record in the db and only proceed with the SLE if they match. You could > also probably do something to turn off 'highcharts plots' just for the > SummaryBy reports, so rather than from [Extras] do it as an option under > the [[]] stanzas. I think both are pretty kludgey though. > > Don't discount a second skin so quickly, it is simple to implement and has > the advantage of eliminating a whole pile of db queries. When we put > together WeeWX-WD we had 8 reports that used a wide variety of data. Some > reports were current point in time and others were full of month, year and > alltime aggregates. We split that into 3 skins, it provided a significant > improvement in generation time because whole lot of unnecessary db queries > no longer occurred. Lazy evaluation of SLE results can improve execution > time but I am not sure they will get around this problem though. > > Gary > -- 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]. For more options, visit https://groups.google.com/d/optout.
