Closed Akilditu closed 2 years ago
Hey there 👋
So in the long-term, we will need to reduce the workload the platform imposes on the API. I will add a result limit (can only GET the last N events) on most API routes.
REgarding the platform, the CI isn't testing the modifications you proposed here so here is a suggestion:
That could be done in a PR later but we should do it at some point 😅
So FYI everyone, we have already merged on the backend API side, the modification to only be able to fetch the last 50 entries instead of loading the whole table. That should speed things considerably
For the rest, including the "for" loops, I'll have to take a closer loop if we can optimize that a bit. But we for sure need to move forward with this PR
So FYI everyone, we have already merged on the backend API side, the modification to only be able to fetch the last 50 entries instead of loading the whole table. That should speed things considerably
For the rest, including the "for" loops, I'll have to take a closer loop if we can optimize that a bit. But we for sure need to move forward with this PR
Hi @frgfm thanks a lot for this, could you confirm the impacted route ?
Hi @frgfm thanks a lot for this, could you confirm the impacted route ?
All the fetch routes (not update, delete, or get) benefit from this :+1: considering the size of tables, fetching media, alerts or events should be much faster now
This PR aims at :
last_ping
timezone to FREnhancements & thoughts :
Thanks feedback and review