Worker failing mysteriously with exceeded CPU time limit.

I'm trying to run this minimal worker:

// Worker
export default {
    async fetch(request: Request) {
        let stopTime = Date.now() + 1; //1ms
        let curTime = Date.now()
        while(curTime < stopTime) {
            curTime =  Date.now()
        }
        return new Response();
    }
};

// Worker
export default {
    async fetch(request: Request) {
        let stopTime = Date.now() + 1; //1ms
        let curTime = Date.now()
        while(curTime < stopTime) {
            curTime =  Date.now()
        }
        return new Response();
    }
};

// Worker
export default {
    async fetch(request: Request) {
        let stopTime = Date.now() + 1; //1ms
        let curTime = Date.now()
        while(curTime < stopTime) {
            curTime =  Date.now()
        }
        return new Response();
    }
};

// Worker
export default {
    async fetch(request: Request) {
        let stopTime = Date.now() + 1; //1ms
        let curTime = Date.now()
        while(curTime < stopTime) {
            curTime =  Date.now()
        }
        return new Response();
    }
};

When this worker is deployed with:

npx wrangler dev --remote=false

npx wrangler dev --remote=false

npx wrangler dev --remote=false

npx wrangler dev --remote=false:

Calls to the worker SUCCEED after ~1ms

npx wrangler dev --remote=true

npx wrangler dev --remote=true

npx wrangler dev --remote=true

npx wrangler dev --remote=true:

Calls to the worker hang for 39 seconds then FAIL with exceeded CPU time limit.

npx wrangler deploy

npx wrangler deploy

npx wrangler deploy

npx wrangler deploy:

Calls to the worker hang for 39 seconds then FAIL with exceeded CPU time limit.

------

Is this intended behavior? What's the reason for this occurring?

kian•1/16/24, 8:36 AM

Answered at workers-and-pages-discussions

usmannkOP•1/16/24, 8:39 AM

oh thanks

Worker failing mysteriously with exceeded CPU time limit.

Similar Threads

Similar Threads

Similar Threads