false alarm so far. mqtt is tied to belchertown. So, seems to be belchertown like you suspected.
Digging more tomorrow. On Monday, May 27, 2024 at 10:00:15 PM UTC-5 Mark Jenks wrote: > I just ripped mqtt out also. I'll check it in the morning and see if that > makes a difference. > > > On Monday, May 27, 2024 at 9:52:21 PM UTC-5 Mark Jenks wrote: > >> Bad news? I uninstalled belchertown, and it's still hitting high CPU on >> mariadb and python3. This is the hit to the DB. >> >> SELECT >> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/select.html> >> * FROM archive WHERE dateTime > 1704088800 AND >> <http://phpmyadmin.mjenks.net/url.php?url=https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html%23operator_and> >> dateTime <= 1735711200 ORDER BY dateTime ASC >> >> >> On Monday, May 27, 2024 at 7:16:36 PM UTC-5 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/f7dd0de8-fc41-4294-bb66-eada9b33eae2n%40googlegroups.com.
