/api/v1/filter/dataset is very slow when customers have a lot of large datasets - causes slowness on data uses tab of systems
When a customer has a lot of datasets, the endpoint: /api/v1/filter/dataset is quite slow to respond because the payload is very large. This causes a significant UX issue on the system details UI.
Data use declarations on systems can be linked with datasets and in order to do this, the UI needs to know which datasets are available. This is happening today with a query to /api/v1/filter/dataset, which you can see when you load an existing system on Fides. If as a user, you wish to add or edit a data use, you then have to wait for the the call to /api/v1/filter/dataset to complete.
It would be preferable if this endpoint contained only the data necessary to relate a dataset to a data use (name, Fides Key, etc). Today it returns the full bodies of all datasets stored in Fides, which I assume is why the payload size becomes so big.
https://ethyca.atlassian.net/browse/PROD-1221