Awesome! I have some questions about the way usage works. I'm wondering if there's a point where efficient, short lived executions are more cost effective as Unbound rather than the bundled Workers now. The docs [1] say:

> Cloudflare will bill for duration charges based on the higher of your wall time or CPU time, with a multiple applied to the CPU time to account for the processing power allotted to your script.

Does anyone know how the CPU time is calculated? What's the "multiple"?

Are there any minimums in terms of execution time? I remember when Workers Unbound was announced I didn't see any mention of minimums anywhere, but other provides have them. For example, Azure [2]:

> The minimum execution time and memory for a single function execution is 100 ms and 128 mb respectively.

I remember thinking the examples in the original announcement assumed no minimums. Even if there's a 100ms minimum, are short lived executions that don't do any waiting on I/O cheaper as Unbound Workers now?

    # Bundled Cost
    $0.50 / 1000000 = 0.0000005 per execution

    # Unbound Per GB-s Cost
    $0.15 / 1000000 = $0.00000015 fixed cost per execution
    $12.50 / 1000000GB-s = $0.0000125 per GB-s (duration cost)

    # 100ms Unbound Cost
    .1s * .125GB = 0.0125 GB-s per execution
    $0.00000015 fixed cost
    $0.0000125 per GB-s * 0.0125 GB-s = $0.00000015625 duration cost
    $0.00000015 fixed + $0.00000015625 duration = $0.00000030625 total cost

Assuming I calculated that right, it's $0.30 per million for 100ms of execution vs $0.50 per million for a normal Worker. There's wall time vs CPU time, but that's a pretty huge discount for short lived executions, right? Am I way off on something? It seems too good to be true. Lol.

1. https://developers.cloudflare.com/workers/platform/pricing#w...

2. https://azure.microsoft.com/en-ca/pricing/details/functions/