advantage of serverless
jonathanstanley
FREEOP

a year ago

The Pricing page says "Pay for compute not servers". However there is also "serverless" which will let a service sleep and "allows you to increase the efficiency"

This still unclear to me.

For example let's set aside the minimum spend for a moment: Suppose I want to setup a server that handles very intermittent webhooks (maybe 1 per day) which can complete within 1-2 seconds. The server isn't doing anything 99% of the time, so maybe it is one of these:

  1. I am only billed for a second or two of CPU a day?

  2. Is there some minimum a CPU is charged while running (ex 10 seconds min)

  3. By keeping the service available (not "serverless"), is the CPU being charged 24x7 (even if not actively processing anything)?

  4. Maybe the CPU winds down to some minimal level just to keep the server running? Is there a minimum like 10% vCPU (similar to how it is shown on the pricing page) ?

Is the purpose of the "serverless" to help shut down servers that are running somewhat pointless background processing rather than actually responding to a webhook? Or is serverless the only way to wind down the CPU to zero?

Solved

1 Replies

chandrika
EMPLOYEE

a year ago

Hey there! With serverless, services are put to sleep when inactive, and billing is based on actual resource usage. There is no minimum CPU charge while the service is running, but there might be a cold start delay when waking up a service. Serverless is designed to optimize costs by shutting down services when not in use.


Status changed to Awaiting User Response Railway 12 months ago


Status changed to Solved jonathanstanley 12 months ago


Loading...