How to optimize performance (maybe caching?) when building a time graph?

Question

Web development

I have data from which the graph is built. Is it necessary to optimize performance somehow? For example, the graph is built for a week, but new data is received every minute and they are displayed. In general, is it considered a heavy load at which it is necessary to cache, if necessary, how to cache this time chart?

Answer 1

The answer will not be unequivocal. Depends on how the script for displaying data from the table is written. It also depends on your hardware.
It is also very important how many rows are in the database, if it is a million, then it is worth caching, because it will be time-consuming to constantly query such a table.
There is very little data in the question.
For example, my story. Internet shop on Bitrix. Has 6 million pictures and all pictures in one folder. This is one disadvantage of the approach to creating a site. Using not the most successful Bitrix functions to request data from infoblocks, AND a 404 page was loaded with any files not found and displayed the entire directory.
As a result, three problem areas in the site, which slowed down the response from the server for 6-9 seconds.
We did not carry out the deepest refactoring of the code and reduced it to 1.5 seconds. Connected caching - 0.4 seconds, page loading.