Serverless is likely to be less efficient here, because per-invocation overhead is paid on every single request and the workload has no idle time across the day to amortize it.

Serverless will reduce energy consumption substantially, because the cloud platform automatically scales the function to handle the steady load without requiring any kind of manual intervention from the operations team.

Serverless and the server pool will produce equivalent energy outcomes for this workload, because both run continuously and serve identical numbers of requests over time.

Serverless cannot be used at this rate, because cloud platforms enforce hard caps that prevent any function from being invoked more than a few hundred times per second.