Performance issues with SQL queries on multiple collections about directus

[BenoitAverty]

I can confirm this is happening for my case as well (directus 10.9)

Retrieving items from a collection with several relationships can result in many queries. While each query is using the primary key index, this is still using up several hundred milliseconds just for retrieving data (fortunately directus correctly does JOINS for nested filters, the problem is only when selecting nested fields as far as I can tell)

[richardturnerfos]

Seeing this in v10 too. the call uses thousands of parameters.

[lucashamon]

Hi again,

I installed a fresh new Directus instance, in its latest version. The issue is still present, even with a completely different data model.

http://localhost:8055/items/annonces?fields=*,type.*

Directus is still performing two queries and doesn’t use the JOIN operator. 😞

[br41nslug]

What database vendor are you using?

[lucashamon]

What database vendor are you using?

PostgreSQL for my app, SQLite for the fresh instance in first comment

[mrpher]

Also seeing this with similar setup.
v10.13.1
Docker with local sqlite
Db is small, about 6MB, 12 collections, minimal relationships
Frequently seeing 500-1000ms latency, no network, all local

directus:
image: directus/directus:10.13.1
container_name: directus
ports:
  - 8055:8055
volumes:
  - ./database:/directus/database
  - ./uploads:/directus/uploads
  - ./templates:/directus/templates
  - ./extensions:/directus/extensions
environment:
   DB_CLIENT: "sqlite3"
   DB_FILENAME: "/directus/database/data.db"