Currently, some backend requests take a huge amount of time when a lot of entities are present.
For example, the dashboard of an admin with all students sometimes takes ages (> 1min) to load with lots of students.
We suspect that this is caused by inefficient querying of data from the database in the backend: when loading entities, you can define which relations are initially loaded, and which relations are lazy-loaded, however there is no batching for the latter.
To improve on this, the following options exist
- configure correctly which relations are loaded with the initial request (ideally most of the required ones for the response of the api call)
- note that this might sometimes not be possible due to circular dependencies
- further limit which data is returned on some api calls (often way more data than required by the frontend)
- this needs investigation which data is actually required by the frontend
Currently, some backend requests take a huge amount of time when a lot of entities are present.
For example, the dashboard of an admin with all students sometimes takes ages (> 1min) to load with lots of students.
We suspect that this is caused by inefficient querying of data from the database in the backend: when loading entities, you can define which relations are initially loaded, and which relations are lazy-loaded, however there is no batching for the latter.
To improve on this, the following options exist