Measuring worker execution time
I have a worker which receives a posted file, does some processing with wasm, and saves it to R2. With a large file, the request can take more than 1 minute to complete, although . It’s an unbound worker, but the docs say the CPU limit is 30s. The request completes without an error. The dashboard doesn’t report CPU usage more than about 4-5s. Is wasm execution time not counted towards CPU time?
1 Reply
Moving stuff to R2 is very I/O intensive. Your worker probably is spending a lot of time waiting while data transfers are happening.