Thanks, to be honest the labels look like **** even without border radius right now.
Please, if you have time, open an issue in the GitHub repo, that way I won’t forget the request.
Okay, yes I’ve been utilizing the shouldUpdate function in LitElement since the initial release of this card, meaning the card is only updated when changes are detected to entities used in the card.
Performance issues could still occur however, especially if you are using several heavily configured cards in the same view.
This particular card can be quite demanding because it has to compute history data, some sensors updates very regularly and could contain 10s/100s of history entries per hour of history. All this history data then has to be computed in order to render the graph. This becomes especially demanding when the card is configured with many entities or with a high hours_to_show
.
Think of a card, containing five sensors with each sensor being updated say 60 times an hour, with hours_to_show
set to 168 (one week), that would result in 30240 history entries. Now, think if you have five similar cards in the same view…you get the point
The problem is most likely caused by a delay when fetching the history from the backend, I’ve experienced that it sometimes can take a while or even timeout completely when fetching the history, especially when being on a bad connection and/or when having a lot of cards all fetching history.