Hi,
Given that your CPU fans are howling, I would confirm which process(es) are
consuming the most CPU. My DBMS lives in memory and hardly consumes any
CPU. OTOH, during report generation, weewx uses a bit for about 20 seconds
(per five minute cycle).
I'd suggest looking for tools to identify the top CPU consumer, resolve it
and go to the next.
---
pablo
On October 12, 2026 10:18:57 Maarten van der Hoeven <[email protected]> wrote:
Ah yes, you are right, forgot my goal. Which is reducing the heavy load on
my host-it-all-machine and get the fans more quiet. Replication is not an
option, as this still means the database (and everything else) runs on the
same host.
Replacing the host is a solution of course.
But besides I want the database load away from my host, my question has
also a curious/technical/want-to-know background. What explains this huge
difference I described? Does it require quite a different database server
setup? I find that hard to believe. To some extent perhaps, but not like 1
record in 10 seconds vs 30 records in 1 second.
Might be I am getting out of weewx scope here...? I could take a look at
SQLite on my host, solving the screaming fans problem another way.
Op maandag 12 oktober 2026 om 15:20:00 UTC+2 schreef John Smith:
You didn't state your goal here, or what configuration you plan to have in
future, but another option is to do MySQL replication between servers.
On Mon, 12 Oct 2026 at 23:47, Maarten van der Hoeven <[email protected]> wrote:
Hi,
WeeWX is running very well. Up-to-date. Archiving record to MySQL-database,
7 million records. Database server created with docker compose,
MySQL-config untouched.
I moved the database to a VPS. Created with the same compose file, so
database server config is identical. Weewx remained on my host. Restoring
the database on VPS took about 15 minutes (acceptable), executed from my host
mysql -uxxx -pxxx -hyyy weewx < weewx.sql (where yyy is IP from VPS)
Now, when I point weewx (still on my host) to the vps database, it sees the
database is 6 hours old (time I made the backup) and it catches up.
Catching up records is extremely slow, about 1 record every 10 seconds.
I dont understand.
- Full restore from host to vps in 15 minutes (about 7500 records a second).
- Catching up (host to vps) 1 record every 10 seconds.
- Catching up (host to host) 20 records a second (more or less)
Any idea what the issue might be?
Database server specs (host and vps) are identical.
Weewx and all compute remained on my host.
Latency to VPS is very good (about 6ms).
Specs VPS: 1 Core, 2Gb RAM,10Gb storage NVMe. (not great, might upgrade,
but first understand this performance difference).
Firewall VPS is irrelevant (did the test with firewall off and on)
Any clues/pointers and I can dig into it. 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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/7a3848f1-415d-4fd4-b029-f3719d313c05n%40googlegroups.com.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/8fa0c196-045c-4896-a0d3-2e7192e7daaen%40googlegroups.com.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/1a130877878.2848.44b74f35a7a433c111dbfaee4cca1c2d%40hillsandlakes.com.
