Replies: 3 comments 1 reply
-
@ryicoh Thanks for sharing this. We are planning on some improvements to query generation when fetching relationships to remove permission rules when they are already enforced through the join condition. I'll try and reproduce your example and get back to you. |
Beta Was this translation helpful? Give feedback.
-
@ryicoh Can you try your queries on this build: |
Beta Was this translation helpful? Give feedback.
-
I tried the build
Below log is the execution plan and the query I used
query HeavyQuery {
SubTask(limit: 10) {
name
body
id
SubTaskAssignees{
User {
name
}
}
Task {
name
TaskAssignees{
User {
name
}
}
}
}
} |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As the title says, I am facing a performance problem.
Even if query is simple like here, execution plan cost is too high(1886261.79..1886261.80)
Below repository includes simple code for reproducing the problem.
https://github.com/ryicoh/hasura-perf
I know the cause is many permission rules.
A execution plan cost without permission is lower(1089.21..1089.22).
Does anyone know a solution to the problem?
Beta Was this translation helpful? Give feedback.
All reactions