What is Wall Time data? Why is it slow?
What is Wall Time data? Why is it slow?
10000ms
9 Replies
Wall Time is real world time where as CPU time is the time that was spent executing your worker. IE if your worker takes 100 ms to complete a request but only 10 ms to complete then you would have Wall Time of 110 ms and CPU time of 10 ms, which you are billed for. In that screenshot, you will be billed for 169ms of CPU time
Does this mean that my network to the worker's network is poor? Is it slow to receive messages?
It means your Worker ran for 10 seconds, we don't know why - you'd need to look at your code.
This is purely the time running the Worker not ingress network time. It may be you're doing a fetch to an origin that's slow, you're waiting on some task for a while, I don't know.
I am confused about the resource restrictions on worker access to CF, do I not need to comply with HTTP restrictions?
what do you mean? which restrictions exactly?
You'll need to return a HTTP response if getting a HTTP request but that's about it
What I mean is, for example, vectorize, it doesn't specify how many times an upsert can be called per second, but HTTP limits it to a maximum of 1200 calls per 5 minutes. I didn't use an HTTP interface, and the worker I used was also limited by the number of HTTP requests per account?
API rate limits do not apply to bindings
but you may hit the subrequest per invocation limit: https://developers.cloudflare.com/workers/platform/limits/#account-plan-limits
Which for Standard is 1000/invocation
Thank you, finally someone knows the restrictions in this area. Do you want to bind operator requests?