Cameron several of us have run v5 with very large db of over 10 years data
on pi4 or lesser boxes without such issue, so a bit more data from you
would be helpful. How big a size are you running ? On what hardware ?
--
You received this message because you are subscribed to the Google Groups
The high cpu usage seems to *relate to the size of the DB*.
I tried with my schema and a new sqlite db - no problems
I migrated my mysql DB to sqlite and got the same problems, if not worse -
elapsed time 18 minutes clock (10 min cpu user, 2 min sys) to run a
default Seasons report and it
Back to the reports themselves.
I am running the GW1000 system without any reports, and will probably end
up running cron jobs to occasionally update the reports.
- I created an empty folder and pointed the config file there.
- This is a heavily customised Seasons report, because it is
I got basically this same result as Vince, trying to run a report manually.
Running as user weewx or root gave same result.
I have no venv, and no pip install.
A pointer to the cause would be that *renaming
/usr/share/weewx/user-2023xxx back to user fixed the problem*.
I also tried a symlink
Indeed! I share your appreciation for Weewx as a Python example. I’m retired, so didn’t have a “need” to learn Python, but did object oriented programming in Smalltalk and then C++ a long while ago, but ended up entering the management track, for good or ill. Nearing retirement, I set up WeeWX on
Thanks, Tom.
I appreciate the tips. Right now I am issuing SQL statements directly into
the 'archive' and 'archive_day_rain' tables
for the barometer trend and day rain values. This works as the access only
occurs with each new record.
My basic understanding of Python is fine, it's all of
A bit more info on the reports.
1. I disabled any reports from the GW1000 and cpu usage dropped to zero.
2. I set the WMR300 to just use the Seasons skin as-shipped, but there
was no improvement.
3. I changed wmr300 config to write to a new empty directory (with
suitable