4 ms·
This is not an area I'm in a lot, so I may be wrong, the cloudflare workers page GP mentioned says that you only get 10ms CPU time per request (or 50ms with the
by chipperyman573 7y ago
This is not an area I'm in a lot, so I may be wrong, the cloudflare workers page GP mentioned says that you only get 10ms CPU time per request (or 50ms with the paid plan). I'm assuming lambda etc have similar limits. So presumably anything that takes longer than 10/50ms.
- ericlewis 7y agolambda can run up to 30m I think (idk about lambda@edge). CF Workers fail when trying to use something like node-unfluff, because the CPU time takes too long. This seems to me, like a more controllable lambda@edge.
- mrkurt 7y agoThe containers on fly.io can go up to 8CPUs. So you can do a lot of computation for images, video etc. They can also accept any kind of TCP traffic (and we're trialing UDP), so lots of interesting network services. This is especially interesting for people who want to do live video. AND we have disks. So you can deploy Varnish, or nginx caches, etc. This is something we enable by hand per app.
- estebarb 7y agoI didn't find documentation about the disks: size, ssd/hdd, price?
- mrkurt 7y agoAh, I didn't make this obvious but that's a feature we're currently testing. We can enable ephemeral disks on apps, but it's not generally available. They're local SSDs, size is variable (still figuring that out). They're free right now. ;) If you want to try them out, you can create an app and then an email to either me or support at fly.io and we'll turn them on for you.