Directus API sluggish when requesting relational data about directus

[rijkvanzanten]

@hmaskat17 Would you be able to share a postgres sql dump of a setup where this is easily reproducible? I haven't seen other reports yet on the same issue, but it could be that you're hitting a specific bottleneck somewhere in this specific schema 🙂

[br41nslug]

Could there be network issues between the directus instance and the database? or perhaps not enough resources available to the directus instance?

[hmaskat17]

Could there be network issues between the directus instance and the database? or perhaps not enough resources available to the directus instance?

Cannot be certain but i don't think it is a network issue since other requests and Directus app work normally. We tested scaling our resources up without any changes. I believe we tested using resources above the recommendation and when monitoring the usage of CPU and memory everything looked fine (not hitting any usage limits).

[hmaskat17]

@rijkvanzanten I'm trying to test the dump file in a Directus instance but I'm not too sure how to create a minimal and viable working dump file that i can share here (that have relational data included). Are there any directus specific database entities needed for the database dump?

[rijkvanzanten]

@hmaskat17 If at all possible, the easiest way for me to be able to reproduce the exact issue is by having a pg_dump that I can just important and have everything 1-1. This is the type of issue that's hard to reproduce without the exact hardware and config, so the closer I can get to your exact setup the better 👍🏻

[hmaskat17]

@rijkvanzanten Understandable but unfortunately we cannot share the whole database here as it is an application in production and contains sensitive data. Will need to debug this issue another way. Do you have any tips on how and where to investigate further?

Since we are almost purely using Directus backend as-is without any hooks etc, I think we can rule out any issues in the code if there are no other reports here either. The only reasoning would be a database schema and configuration problem? So we should probably try testing schema changes and debugging database?

We are temporarily setting up a custom endpoint extension in Directus to retrieve the same relational data and it is currently returning data in ~500 ms.