Kian: Ok interesting. This problem reminds me of when I tried to make fetch request directly to othe

Kian: Ok interesting. This problem reminds me of when I tried to make fetch request directly to other workers within the same zone. The external API in this case is actually done through a proxy worker within the same zone. But I understand you are saying that there should be no difference depending on how it's triggered

kian•3/3/23, 9:42 AM

Fetching same-zone as in custom routes or workers.dev?

kian•3/3/23, 9:43 AM

Either way, that'd get a 522 error rather than a 404 iirc

danielsundqOP•3/3/23, 9:45 AM

Custom routes. Ok good to know

danielsundqOP•3/3/23, 9:46 AM

I will look for a solution elsewere then

Ddanielsundq Kian: Ok interesting. This problem reminds me of when I tried to make fetch requ...

Hello, I’m Allie!•3/3/23, 11:11 AM

Could the service you are

fetch

fetch

ing be region-locked? The Cron Worker might run in a different datacenter than where your regular HTTP-triggered Workers requests run.

Kavatch•3/3/23, 11:33 AM

How do workers perform when it comes to CPU heavy tasks? Like I want to encode a GIF which takes around 10 sec on my local PC, but when I run it on a Server with quite a good CPU it get it down to ~2 seconds.
If I now ran it inside a worker, would I rather see an increase in time for encoding, or a drop-off in time required?

Kavatch•3/3/23, 11:35 AM

I am using Rust, if that makes any difference

KKavatch I am using Rust, if that makes any difference

Hello, I’m Allie!•3/3/23, 11:43 AM

WebAssembly takes a heavy initial hit, because you have to translate your JS objects into ArrayBuffers to pass in. Should perform fine though.

Kavatch•3/3/23, 11:48 AM

My main concern is just that I might hit the 30 sec timeout limit (for HTTP requests) if the encoding is slower on workers than on my PC, for example.
And since I am unable to find any concrete numbers on the CPU performance on the website, my best bet was that maybe here someone knows if how they perform on that type of task or even has some experiences with that kind of workers.

KKavatch My main concern is just that I might hit the 30 sec timeout limit (for HTTP requ...

Jadugar_Jaggu•3/3/23, 11:50 AM

Use cron triggers (hourly setting) to increase time limit

KKavatch My main concern is just that I might hit the 30 sec timeout limit (for HTTP requ...

Hello, I’m Allie!•3/3/23, 11:50 AM

As an example of what Workers+WASM can do, you can check out https://og-playground.vercel.app/. In general, CF won't provide direct CF metrics, but I would say, for light/moderate loads, go with Workers+WASM, for heavy+ loads, go with something like https://fly.io

Vercel OG Image Playground

Generate Open Graph images with Vercel’s Edge Function.

KKavatch My main concern is just that I might hit the 30 sec timeout limit (for HTTP requ...

Jadugar_Jaggu•3/3/23, 11:52 AM

I use a task that takes 10 to 12 minutes using a worker. I just do it once an hour using cron triggers and KV

JJadugar_Jaggu I use a task that takes 10 to 12 minutes using a worker. I just do it once an ho...

Hello, I’m Allie!•3/3/23, 11:54 AM

The issue is the CPU Time. AFAIK, you still only get 30 seconds of CPU with Cron Triggers.

Hello, I’m Allie!•3/3/23, 11:55 AM

NVM

HHello, I’m Allie!As an example of what Workers+WASM can do, you can check out https://og-playgrou...

Kavatch•3/3/23, 11:55 AM

I will have a look at these sites , thank you!

Hello, I’m Allie!•3/3/23, 11:55 AM

I read the wrong section

Jadugar_Jaggu•3/3/23, 11:55 AM

he is asking for http request timeout

Jadugar_Jaggu•3/3/23, 11:55 AM

not cpu

Hello, I’m Allie!•3/3/23, 11:55 AM

Yeah, misread, sorry!

JJadugar_Jaggu Use cron triggers (hourly setting) to increase time limit

Kavatch•3/3/23, 11:57 AM

In general a good Idea however since I want to encode "on demand" I probably can't use cron jobs since I want to do it every time a user calls an endpoint. Thanks though!

KKavatch In general a good Idea however since I want to encode "on demand" I probably can...

Jadugar_Jaggu•3/3/23, 12:01 PM

If you want to do it on demand you can give a try to Queue. Cause in it consumer worker also support waitUntil() like cron

I am not that sure but you can try it

Jadugar_Jaggu•3/3/23, 12:03 PM

Just need to set the value of Message batch size to 1

NNicolaas Hi guys, is there any way to use a worker to make sure that requests going to ou...

Hello, I’m Allie!•3/3/23, 12:44 PM

You can use a CF Tunnel for that? Then you don't need to open any ports either.

Hello, I’m Allie!•3/3/23, 12:44 PM

For extra security, you can verify an Access JWT too.

NNicolaas Hi guys, is there any way to use a worker to make sure that requests going to ou...

DaniFoldi•3/3/23, 1:10 PM

You can also check out the new mTLS binding?

kian•3/3/23, 1:30 PM

I don't see it thrown from the runtime - that looks like it's thrown by wasm-bindgen

kian•3/3/23, 1:31 PM

Unless it's just thrown by V8 itself, which would be odd

kian•3/3/23, 1:34 PM

kian•3/3/23, 1:34 PM

Yeah, that's wasm-bindgen

kian•3/3/23, 1:37 PM

wasm-bindgen isn't something that is included in workerd

kian•3/3/23, 1:38 PM

Are you using WASM in your Worker?

kian•3/3/23, 1:47 PM

Is the image that fails larger than the rest?

kian•3/3/23, 1:53 PM

I'd have a global variable of initializedinitialized and only init inside an if check

kian•3/3/23, 1:54 PM

import esbuild from "esbuild-wasm";
import wasm from "../node_modules/esbuild-wasm/esbuild.wasm";

let initialised = false;
globalThis.performance = Date;

export default {
    async fetch(): Promise<Response> {
        if (!initialised) {
            await esbuild.initialize({
                wasmModule: wasm,
                worker: false,
            });
            initialised = true;
        }
        return new Response("Hello World");
    },
};

import esbuild from "esbuild-wasm";
import wasm from "../node_modules/esbuild-wasm/esbuild.wasm";

let initialised = false;
globalThis.performance = Date;

export default {
    async fetch(): Promise<Response> {
        if (!initialised) {
            await esbuild.initialize({
                wasmModule: wasm,
                worker: false,
            });
            initialised = true;
        }
        return new Response("Hello World");
    },
};

Example from https://blog.interactions.rest/blog/esbuild-on-the-edge/

NNicolaas Hi guys, is there any way to use a worker to make sure that requests going to ou...

Kavatch•3/3/23, 2:00 PM

It sounds like what you want is something along the lines of this here: https://developers.cloudflare.com/ssl/origin-configuration/origin-ca/#4-required-for-some-add-cloudflare-origin-ca-root-certificates
With that you can edit the configuration on your server to validate the certificate from cloudflare before accepting the request and thus preventing anyone from sending request not though cloudflare.
For example in Nginx you would add something like this to the server configuration:

ssl_client_certificate /etc/ssl/certs/cloudflare-origin.pem;
ssl_verify_client on;

ssl_client_certificate /etc/ssl/certs/cloudflare-origin.pem;
ssl_verify_client on;

About all of this there is also this excellent blog post: https://blog.jfx.ac/securing-nginx-origin-with-cloudflare.html

jfx Blog

How to secure your nginx + Cloudflare configuration to stop any ori...

I decided to write this as although a lot of guides on the internet provide a solid configuration for an nginx server, most of these guides will result in an IP leak somewhere under their configuration for the origin server somewhere. So you got your nginx server setup (hopefully) and it’s serving your files (or being an effective reverse proxy)...

Origin CA certificates · Cloudflare SSL/TLS docs

Use Origin Certificate Authority (CA) certificates to encrypt traffic between Cloudflare and your origin web server and reduce origin bandwidth …

kian•3/3/23, 2:05 PM

Bleh, might not work with svg2png then.

import esbuild from "esbuild-wasm"; import wasm from "../node_modules/esbuild-wasm/esbuild.wasm"; let initialised = false; globalThis.performance = Date; export default { async fetch(): Promise<Response> { if (!initialised) { await esbuild.initialize({ wasmModule: wasm, worker: false, }); initialised = true; } return new Response("Hello World"); }, };

Kian: Ok interesting. This problem reminds me of when I tried to make fetch request directly to othe

Similar Threads

Similar Threads

Similar Threads