weewx take really long time to update

[hajsek...@gmail.com]

I use weewx 5.2.0 and interceptor and sofaskin.
I have alot of graphs and data on my website and that is a problem because it takes more than 23 min, to process all of those graphs and data.
And I see weewx process all from current than next is week than is month and year takes mostly alot time to finish.
Is there a option to start making all at the same time not serial so weewx can use more CPU and RAM and it finishes quicker.
When I enable debug 3 there is no errors about it.
https://vreme.povej.net

[John Smith]

Slow to process isn't an error, as per my comment on your issue, you need to give us a lot more to go on for what looks like a case of missing DB columns, a debug log covering a full archive period, with passwords and other sensitive details redacted, along with the skins you're using would be a good first step.

--
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 weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/947e9a4c-c84d-4c86-858f-378477eb6157n%40googlegroups.com.

[hajsek...@gmail.com]

Hi

Thank you for your answer I see I need to send more data for it.
here is weewx log long  https://privatebin.povej.net/?9551e9712c791916#49bPxHs7Wqy7yTXdLufLyuncqJDFXtLkiCU4HRjUYk7F
here is also weewx.conf  https://privatebin.povej.net/?ac1f7b31e7762539#9o5hxRB86CXJog5JNUtrUB3EnXH7yT4MMhSykqk5TRdR

here is short version
 journalctl -u weewx -f | grep -iE "debug|report|image|generator|plot|skin|time"
jan 15 13:19:20 web.povej.net weewxd[237372]: DEBUG user.rtgd: received archive record: {'dateTime': 1768479540, 'usUnits': 16, 'pressure': 951.0466267552601, 'outHumidity': 79.0, 'inHumidity': 45.0, 'outTemp': 5.7222222222222205, 'inTemp': 24.777777777777775, 'windSpeed': 4.02336, 'windDir': 26.0, 'windGust': 4.988966400000001, 'windGustDir': 26.0, 'radiation': 300.32, 'rain': 0.0, 'rainRate': 0.0, 'UV': 2.0054, 'extraTemp1': 22.77777777777778, 'extraTemp2': 20.72222222222222, 'extraTemp3': 17.388888888888886, 'extraHumid1': 51.0, 'extraHumid2': 33.0, 'soilMoist1': 53.0, 'pm2_5': 3.5, 'pm10_0': 4.0, 'co2': 1433.0, 'extraTemp4': 19.111111111111114, 'extraHumid3': 43.0, 'extraHumid4': 44.0, 'lightning_last_distance': 20.0, 'lightning_strike_count': 0.0, 'lightning_last_time': 1767460184.0, 'wh57_battery': 5.0, 'leak_battery_1': 5.0, 'leak_ch1': 0.0, 'leak_battery_2': 5.0, 'leak_ch2': 0.0, 'co2Temp': 22.388888888888886, 'co2Humidity': 55.0, 'co2Battery': 6.0, 'pm10_0_24h': 4.0, 'co2_24h': 1118.0, 'pm2_5_out': 10.0, 'pm25_avg_24h_ch1': 10.5, 'pm25_battery': 5.0, 'battery_1': 0.0, 'battery_2': 0.0, 'battery_3': 0.0, 'battery_4': 0.0, 'windDir10': 62.0, 'windSpeed10': 1.7702784000000003, 'maxDailyGust': 5.1, 'eventRain': 0.0, 'hourlyRain': 0.0, 'weeklyRain': 0.106, 'monthlyRain': 0.276, 'wh90_battery': 3.18, 'hrain_piezo': 0.0, 'drain_piezo': 0.0, 'wrain_piezo': 0.004, 'ws90_cap_volt': 3.3, 'ws90_version': 155.0, 'radio_freq': None, 'station_model': None, 'soil_battery_1': 1.5, 'altimeter': 985.4041179069617, 'appTemp': 3.3284745935433433, 'barometer': 986.1759284454562, 'cloudbase': 705.1146933859411, 'dewpoint': 2.366614362668351, 'ET': 0.00012327228690709184, 'heatindex': 4.412777777777777, 'humidex': 5.7222222222222205, 'inDewpoint': 12.027587969086376, 'maxSolarRad': 281.50060490200303, 'windchill': 5.7222222222222205, 'windrun': 0.067056, 'interval': 1.0}
jan 15 13:19:20 web.povej.net weewxd[237372]: DEBUG weewx.restx: StationRegistry: wait interval (1260 < 86400) has not passed for record 2026-01-15 13:19:00 CET (1768479540)
jan 15 13:19:20 web.povej.net weewxd[237372]: DEBUG user.rtgd: windrose data calculated: [114.1, 396.4, 551.4, 404.9, 427.4, 326.9, 188.9, 122.8, 166.7, 96.4, 42.6, 5.5, 1.8, 0.0, 5.8, 6.4]
jan 15 13:19:20 web.povej.net weewxd[237372]: DEBUG user.rtgd: queued min/max barometer values: {'min_barometer': 881.627415487216, 'max_barometer': 1047.03882395463}
jan 15 13:19:20 web.povej.net weewxd[237372]: DEBUG user.rtgd: received stats package: {'min_barometer': 881.627415487216, 'max_barometer': 1047.03882395463}
jan 15 13:19:20 web.povej.net weewxd[237372]: INFO weewx.engine: Launch of report thread aborted: existing report thread still running
jan 15 13:19:20 web.povej.net weewxd[237372]: DEBUG weewx.restx: Ambient: url: https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw&ID=IDOMALE9&PASSWORD=XXX&softwaretype=weewx-5.2.0&baromin=29.122&dateutc=2026-01-15%2012%3A19%3A00&dailyrainin=0.00&dewptf=36.3&rainin=0.00&humidity=079&tempf=42.3&AqPM10=4.0&AqPM2.5=3.5&solarradiation=300.32&soilmoisture=053&UV=2.01&winddir=026&windgustmph=3.1&windspeedmph=2.5
jan 15 13:19:20 web.povej.net weewxd[237372]: DEBUG weewx.restx: Wunderground-PWS url: 'https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw&ID=IDOMALE9&PASSWORD=np8xkt1j&softwaretype=weewx-5.2.0&baromin=29.122&dateutc=2026-01-15%2012%3A19%3A00&dailyrainin=0.00&dewptf=36.3&rainin=0.00&humidity=079&tempf=42.3&AqPM10=4.0&AqPM2.5=3.5&solarradiation=300.32&soilmoisture=053&UV=2.01&winddir=026&windgustmph=3.1&windspeedmph=2.5'
jan 15 13:19:30 web.povej.net weewxd[237372]: DEBUG user.interceptor: empty queue

četrtek, 15. januar 2026 ob 12:28:21 UTC+1 je oseba John Smith napisala:

[John Smith]

Some quick observations after skimming the links you provided, this might be the main culprit:

windrose data calculated: [112.0, 387.7, 540.3, 402.0, 427.4, 326.9, 193.3, 133.4, 189.4, 96.4, 52.8, 9.0, 1.8, 0.0, 5.8, 6.4]

Not sure if this is an issue or not:

INFO weewx.engine: Record generation will be attempted in 'software'

 This is definitely a cause of excessive processing:

INFO weewx.engine: Using archive interval of 60 seconds (software record generation)

If you need frequent updates I suggest you look into MQTT or similar.

 

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/3f344f64-56ba-4289-8e9b-2d41f2e80896n%40googlegroups.com.

[hajsek...@gmail.com]

thank you for your answer, but I really have no clue what are you saying, what can be a problem.

I have set in wewx update every 3 minutes I tested  it on 1 minute.

Also I don't know what you mean with MQTT?
I like to use weewx and sofaskin and I put more than a month every day for many hours to have site like it is now and I don't want to use something else and make all over again.
thats why I asked here if somebody can help me somehow.

thank you

četrtek, 15. januar 2026 ob 13:59:18 UTC+1 je oseba John Smith napisala:

[michael.k...@gmx.at]

Some persons consider update intervals smaller than the default 5 minutes excessive. I'm also on "team excessive". What ist your use case for an update interval? If the use case is having close-to-real-time-data, there are very likely better solutions. Some skins provide (almost) real time updates for observations, this is done by emitting MQTT packets from the weewx back end service to an MQTT client in the front end (the web page). see https://github.com/weewx/weewx/wiki#skins for skin with "live weather feed".

If your use case really depends on setting the archive_interval lower than 300 seconds, it's another story.

[hajsek...@gmail.com]

thank you for explanation.
but still if I setup 5 minutes, I think there still won't be any difference bacause all is taking 23 minutes to update that web page.
I really like to keep this sofaskin because like I said it takes alot of hours to finally manage to get what I have now.
So I am searching for some solution here, maybe to update week and month  and year evey hour and current for every 5 minutes.

četrtek, 15. januar 2026 ob 15:53:16 UTC+1 je oseba michael.k...@gmx.at napisala:

[michael.k...@gmx.at]

I remember there were performance issues with the Belchertown skin after v5.2.0. I can't remember the underlying issue, but maybe there is something similar with the sofaskin.

[hajsek...@gmail.com]

thank you for your info.

Where I can get more info about that or who can help to solve this?

regards

četrtek, 15. januar 2026 ob 19:17:41 UTC+1 je oseba michael.k...@gmx.at napisala:

[Karen K]

hajsek...@gmail.com 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.

[Vince Skahan]

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.

[hajsek...@gmail.com]

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:

[John Smith]

I'd start by disabling the windrose section in your skin, you don't need to switch skins just work out what's slow.

If that speeds things up you then you just need to work out what columns it needs in the DB.

--
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 weewx-user+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/40b69162-2c3a-464d-bd3f-ea19e3e46ffbn%40googlegroups.com.

[R]

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

[Tom Keffer]

See https://github.com/weewx/weewx/wiki/v5-performance-troubleshooting for a discussion of V5 performance issues.

--
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 weewx-user+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/bb859670-ae88-4b2e-a5c2-554f79cec820n%40googlegroups.com.