Maarten van der Hoeven <[email protected]> writes: > 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.
It does not really make sense to compare restoration speed with transaction speed. I would ignore "load speed and transaction speed are different" and instead look at "what is causing my transaction speed to be what it is". Besides the index comment which seems wise, you haven't established if the problem is from round trips or from database execution time. > 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. It doesn't make sense that mysql just being the weewx database should take so much cpu time. Unless you are running reports that aggregate data over all time maybe, but the solution is "don't do that". -- 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/rmi7bjnnf49.fsf%40s1.lexort.com.
