Is it right to store view information in mysql database?

Question

MySQL

I have a view system on my site, it is linked to accounts. And there are already more than 2 million records in the database. Whether the basis with so many records will be heavily loaded? While there were few entries, the calculation went directly in the request, but now I think we need to rewrite the system so that static data is stored in the profile itself. How do you advise to do?

Answer 1

It is perfectly normal, instead of executing an analytics request at the time of the output, to do it as a trigger during the data change, in the corresponding field.
This is justified since the number of read requests is several times higher than the number of changes, especially when analytics requests a lot of data ... i.e. almost always.
Disk space is orders of magnitude cheaper than CPU time (and the operating time of this disk), which you will spend on analytics.