You might also swap out your database with an empty one to see if the
volume of data in the database is causing the slowness. I really doubt it,
though.

On Wed, Jan 17, 2024 at 2:32 PM vince <vinceska...@gmail.com> wrote:

> Michael -  guessing you have something customized under the hood causing
> this.  Again you have a few choices....
>
>    - disable Belchertown (temporarily) and see if it goes away
>    - switch to the Simulator (temporarily) after saving your weewx setup
>    and see if it's related to the Acurite stuff you're using
>    - disable everything 'except' weewx (temporarily) and see if it goes
>    away
>    - throw hardware at it and get a faster computer.  You might even be
>    paging on a pi3 and a 4GB pi4 or pi5 might be enough
>
> Kinda impossible to know with skeletal data to look at, but these things
> can be difficult to dig into.
>
> I did cause something similar yesterday trying to run on a pi5 where the
> StdReport never finished in even 5 minutes but didn't figure out why.  I
> 'think' it was something related to having ancient simulated data in the db
> from timesync issues (2014 dates in the NOAA files is definitely wrong) and
> switching to a different driver.  Moving the old db aside seemed to help,
> but again I didn't dig much into it yesterday on a test system.
>
> On Wednesday, January 17, 2024 at 12:37:35 PM UTC-8 Tom Keffer wrote:
>
>> Maybe, although I've run V5 without any problems on a RPi Zero! There's
>> something in your Belchertown skins that is triggering the long runtimes.
>>
>> On Wed, Jan 17, 2024 at 6:42 AM Michael Sanphillipo <sanph...@gmail.com>
>> wrote:
>>
>>> FWIW I went back to 4.10.2 and no more database errors and the CPU
>>> spikes are gone. Might be time to upgrade to a PI4 or PI5.
>>>
>>> On Tuesday, January 16, 2024 at 5:41:39 PM UTC-5 Tom Keffer wrote:
>>>
>>>> The difference is that V5 could be doing more. We don't know for sure,
>>>> yet, but it is probably reporting on synthetic types, which V4 was unable
>>>> to do.
>>>>
>>>> On Tue, Jan 16, 2024 at 2:36 PM sanphillipo <sanph...@gmail.com> wrote:
>>>>
>>>>> Yes I'm on a PI3 with ADSB tracking running as well. I changed the
>>>>> archive to 300 so we'll see how it goes. Never had the issue before
>>>>> upgrading to 5.0 so it must be somewhat related to that.  I've noticed 
>>>>> that
>>>>> CPU usage and temps are slightly higher than average since I upgraded last
>>>>> night. Thanks for the suggestions.
>>>>>
>>>>>
>>>>>
>>>>> Sent from my Verizon, Samsung Galaxy smartphone
>>>>>
>>>>>
>>>>> -------- Original message --------
>>>>> From: vince <vince...@gmail.com>
>>>>> Date: 1/16/24 4:12 PM (GMT-05:00)
>>>>> To: weewx-user <weewx...@googlegroups.com>
>>>>> Subject: Re: [weewx-user] Re: Database Error Message
>>>>>
>>>>> The log excerpt is a little short but perhaps.   I see in your log you
>>>>> have a 120 second archive period yet Belchertown took 125 seconds to run
>>>>> (which is 'very' slow), so it's possible your archive period is too fast
>>>>> for your hardware.  What kind of pi are you on ?  Something slower than a
>>>>> pi4 perhaps ?
>>>>>
>>>>> If you are on slow hardware try disabling Belchertown temporarily and
>>>>> see if the problem goes away.  Or alternately set your archive period to
>>>>> perhaps 180 seconds and try that.  Or as always you might throw hardware 
>>>>> at
>>>>> it and use a faster pi....but it looks like you're asking your hardware to
>>>>> do too much too often.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to a topic in the
>>>>> Google Groups "weewx-user" group.
>>>>> To unsubscribe from this topic, visit
>>>>> https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>> weewx-user+...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%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+...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/weewx-user/65a704ff.050a0220.9fe86.27f4%40mx.google.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/65a704ff.050a0220.9fe86.27f4%40mx.google.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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/11b0239b-0bd7-4d2f-a5ee-12cc99e402aan%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/11b0239b-0bd7-4d2f-a5ee-12cc99e402aan%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/c83f7ccc-1a74-4045-ae7e-957631e7bf8cn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/c83f7ccc-1a74-4045-ae7e-957631e7bf8cn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM20jF%2BuMPJJ%3D%2Bh32TXAB%3DuW5cPj8EH1WQ4%2BT1%2Br-piwXYg%40mail.gmail.com.

Reply via email to