Cloudflare Developers•2y ago

I was just hit with a much larger than

I was just hit with a much larger than expected bill, suggesting crazy high DO runtime... yet looking through each project, and each DO, I can't find one that could even be close to being the culprit. Is there a way to diagnose where the spend/compute time is coming from??

5 Replies

Kevin•2y ago

And also how is webosocket time shown/reflected? I see stats for requests, but sockets wouldn't count in this (aside from perhaps the initial request)

Unknown User•2y ago

Message Not Public

Kevin•2y ago

Yeah looked through the durations in the dash, even across blocks of the time range (previous month) for each DO... nothing comes close

Unknown User•2y ago

Message Not Public

Unsmart•2y ago

Not sure if the dash does for you but for me I am not even allowed to query all of december only with the graphql api I can. But it is also nicer because the graphql api can tell you which objects used the most wall time I do still have to make 2 requests on the graphql api because the limit is 30 days not 31 but 🤷

query {
  viewer {
    accounts(filter: {
      accountTag: "<tag>"
    }) {
      durableObjectsInvocationsAdaptiveGroups(filter: {
        date_geq: "2022-12-01",
        date_leq: "2022-12-30"
      }, limit: 10000, orderBy: [max_wallTime_DESC]){
        dimensions {
          namespaceId
          scriptName
          objectId
          date
        }
        sum {
          wallTime
        }
      }
    }
  }
}

query {
  viewer {
    accounts(filter: {
      accountTag: "<tag>"
    }) {
      durableObjectsInvocationsAdaptiveGroups(filter: {
        date_geq: "2022-12-01",
        date_leq: "2022-12-30"
      }, limit: 10000, orderBy: [max_wallTime_DESC]){
        dimensions {
          namespaceId
          scriptName
          objectId
          date
        }
        sum {
          wallTime
        }
      }
    }
  }
}

Gaming

Programming

I was just hit with a much larger than