For better or worse, Unbound's billing is designed to be apples-to-apples comparable to Lambda. Lambda bills for real time (or, technically, memory-time), not f

For better or worse, Unbound's billing is designed to be apples-to-apples comparable to Lambda. Lambda bills for real time (or, technically, memory-time), not for CPU usage. Although, for 128MB instances, Lambda throttles the CPU to something like 1/8 speed. Since Workers doesn't throttle, Workers Unbound billing is actually based on either real time or 8x CPU time, whichever is larger, in order to maintain direct comparability. On the other hand, CPU limits are based on CPU time. In the original "Bundled" pricing model, we didn't charge for time, but we did limit CPU time to 50ms. Unfortunately, we discovered that very few people actually understand what this means, and most users assumed we were limiting real time to 50ms, leading to a lot of confusion. So that was another motivation for basing billing on real time instead.