A few observations. You are running the realtime gauge data extension usually used with the SteelSeries weather guages. You don't appear to be using the SteelSeries gauges on your site. The realtime gauge data extension won't be directly increasing report generation times but it is another service that is loading the CPU so other processes (eg WeeWX report generation) has less CPU resources so hence takes longer. Disable the realtime gauge data extension. As an aside it is the realtime gauge data extension that is generating the wind rose data that people seem to be fixated on.
Your sofa skin is being run under the 'SeasonsReport' report name. So any comparison of generic Seasons performance against your (apparent) 'SeasonsReport' data is meaningless. Your site has 25-26 plots per day/week/month/year (Seasons typically has half that) so that will be a significant extra load. Your log extract (the 'long' one) shows a WeeWX startup but then jumps in time to when report threads are being aborted. So we never actually see the first report thread log output (well we see part of it where the SeasonsReport takes 300 odd seconds). Either post the entire log from startup until that first SeasonsReport thread completes or restart WeeWX and then post the entire log from startup until that first SeasonsReport thread completes. That way we can see what else is in that report thread that might be taking an excessive amount of time to generate (you appear to have a number of report enabled under StdReport, who knows what they are doing without seeing a log). Following on from the last point I suggest you change [[SeasonsReport]] under [StdReport] to something like [[SofaskinReport]], that way your logs will be less misleading. Overall it seems to me you have a config that has accumulated a lot of detritus over time with a lot of that detritus still being enabled despite not being used. If you clean that up I think you will find things improve noticeably. R On Friday, 16 January 2026 at 07:29:16 UTC+10 [email protected] wrote: > Hi > Thank you for your advice I have added missing tables in mysql but still > takes 20 minutes to update web site. > What can I disable for testing to see what is problem or somehow get time > which part takes longest? > > četrtek, 15. januar 2026 ob 20:15:56 UTC+1 je oseba Vince Skahan napisala: > >> INFO weewx.cheetahgenerator: Generated 11 files for report SeasonsReport >> in 306.91 secondsThis is almost impossible unless you have altered your >> system or your skin. Seasons is 'very' fast. >> >> Your weewx.conf shows only 96 elements in your db. The wview_extended >> schema has 114, so I'm assuming you have manually (needlessly) tried to >> delete columns you didn't think were needed. If your skin tries to report >> something not in an element in the db, things will get 'very' slow. >> >> I can't guess which item(s) might be missing in your schema but I've >> attached what you reported in the earlier thread, sorted alphabetically to >> be easier to look through. >> >> On Thursday, January 15, 2026 at 10:54:42 AM UTC-8 Karen K wrote: >> >>> [email protected] schrieb am Donnerstag, 15. Januar 2026 um 19:29:20 >>> UTC+1: >>> >>> Where I can get more info about that or who can help to solve this? >>> >>> >>> John Smith explained a possible reason in the 2nd post: In your database >>> may be some columns missing. That results in WeeWX calculating them "on the >>> fly", and that takes time. Look into the file wview_extended.py and >>> check if all columns there are really present in your database. >>> >>> -- 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 visit https://groups.google.com/d/msgid/weewx-user/bb859670-ae88-4b2e-a5c2-554f79cec820n%40googlegroups.com.
