Replies: 3 comments
-
|
All time based metrics requires heavy database queries and if the database index doesn't match the query it is unavoidable that you see slow loading. You have to look into improving the database queries based on the required use case. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The database queries it does are on a very light table with all columns indexed. All metric
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Description:
My main dashboard has a lot of cards (22 atm) and which exist of 19 trend cards. It seems on the first load the page is loading at around 1 - 1.25s and then it start loading the cards. But somehow it's very slow on the first request. See the timeline / waterfall.
If I try to open a single card after I clear the cache it only takes ~400ms to get the data instead of 4 - 5s. I'm using a default forge web server at Linode (dedicated 4 CPU / 8GB ram) with a very low load.
Detailed steps to reproduce the issue on a fresh Nova installation:
Beta Was this translation helpful? Give feedback.
All reactions