You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the following query takes around 3 seconds:
SalesOrders(first: 10) {
totalCount
edges {
node {
name
address_name {
name
address_title
address_line1
address_line2
pincode
city
}
}
}
}
What's especially interesting is, that fetching many subfields (in this case 6 from address_name) is much slower than just fetching a few - so it seems, that the db is queried individually for each subfield, which probably is what makes it so much slower.
Just querying a single subfield of address_name takes around 1 - 1.2 seconds. It's still slow, but bearable.
Not querying subfields at all is around 300 ms. So >700 ms for 10 additional docs is still a lot but I don't know if that can be sped up easily by fetching multiple docs at once. But in this case it would still be faster to send 10 parallel REST queries to the server, which get answered in around 150 ms simultaneously.
The text was updated successfully, but these errors were encountered:
Running the following query takes around 3 seconds:
What's especially interesting is, that fetching many subfields (in this case 6 from address_name) is much slower than just fetching a few - so it seems, that the db is queried individually for each subfield, which probably is what makes it so much slower.
Just querying a single subfield of address_name takes around 1 - 1.2 seconds. It's still slow, but bearable.
Not querying subfields at all is around 300 ms. So >700 ms for 10 additional docs is still a lot but I don't know if that can be sped up easily by fetching multiple docs at once. But in this case it would still be faster to send 10 parallel REST queries to the server, which get answered in around 150 ms simultaneously.
The text was updated successfully, but these errors were encountered: