Wild guess here. Belchertown writes its own NOAA directory with its own copies of those files that it creates, so verify that you have all the year and month files for all your data in the NOAA dir under the belchertown output directory. It’s ok to prepopulate it from old copies as needed to speed things up.
I have almost 18 years of data in sqlite3 locally on SD and the pi4 doesn’t work too hard every archive period keeping up with belchertown, a custom hacked variant of standard, a couple extensions and other skins, and both mqtt subscribe and publish. On Monday, May 27, 2024 at 5:16:36 PM UTC-7 Tom Keffer wrote: > That query is asking for every single record over 4 years of data --- > about 400,000+ records with a 5 minute archive interval. That's not the use > pattern when an xtype is causing the problem > <https://github.com/weewx/weewx/wiki/XTypes-performance>. > > It's hard to imagine why the Belchertown skin would need data at that > density. Try isolating the problem by shutting off the imagegenerator, then > the cheetahgenerator (you can do that by modifying generator_list in > skin.conf). > > Then once you know which one is the culprit, then start trimming their > respective sections in skin.conf until you isolate the plot or tag that is > causing the problem. > > On Mon, May 27, 2024 at 4:47 PM Mark Jenks <mjenk...@gmail.com> wrote: > >> Just built a new weewx on my Fedora 38 this morning, and attached it to >> my mariadb. It has 13 years worth of data in it. >> >> I am running Belchertown and mqtt, and installed Windy. But I just >> removed Windy to see if that was it, but still does it. Python and/or >> moriadb goes to 100% CPU. >> Mariadb says the high query during that time is: SELECT * FROM archive >> WHERE dateTime > 1320346500 AND dateTime <= 1716824400 ORDER BY dateTime ASC >> But that makes no sense, since I can query my entire archive table >> (select *) in about 3 seconds. >> >> Any thoughts on how to catch what is going on? I could enable debug, >> but hoping for a better way other that looking at a ton of logs. >> >> Thanks! >> >> >> >> -- >> 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 on the web visit >> https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/a882fb44-d36b-4bf4-8588-41199524b5f7n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d1402c6b-b128-43bd-a683-8e901ad131cdn%40googlegroups.com.
