I am after some confirmation on my understanding and possible advice I am using Shopfy graphql and I under stand the notion of leaky bucket and throttling. When I conduct some calls (see below as an example) the difference between requestedQueryCost and actualQueryCost looks quite large, for example requestedQueryCost of 125 and an actualQueryCost of 6 My understanding is that when a bucket is checked, to see if there is space, it is the requestedQueryCost value that is used. There seems to be a big gap between the two values meaning that a call can be rejected, even though there is plenty of space based on the actualQueryCost. I know I can streamline the request, for example only ask for some metafields, rather than all of them, for example just requesting 2 metafields gives me requestedQueryCost of 25 and an actualQueryCost of 5, which is better. My general feeling is that if I want a lot of information I can quickly hot the limit. For example to update lots of metadata fields I would need to get them, get their IDs and then update them. Am I missing something? Thanks Grant {
productByHandle(handle: "%s"){
id
title
handle
metafields (first:100){
edges {
node {
description
id
key
legacyResourceId
namespace
value
valueType
}
}
}
resourcePublications (first:10) {
edges {
node {
publishDate
publication{
id
name
}
}
}
}
}
}
... View more
