question

First, I'd recommend using Azure Functions Cloud Script, as it has a number of advantages. Better monitoring and reporting for things like this is one of them. For legacy Cloud Script, the total memory used will be the size of the total script, plus all memory allocations within it, plus some overhead for the V8 engine itself. For runtime, it's a single-threaded process in a single VM, so the CPU consumption is the same throughout its runtime. As to how hard the CPU is being hit depends upon what you're doing. For example, if you make an http.request() call, the CPU is going to be idling while you wait on the response to that external call, but that's still consumed runtime, since the engine is 100% dedicated to your script until it's done.

But all that aside, I suspect you're not exceeding the base memory per execution, which is 128 MB (https://docs.microsoft.com/en-us/gaming/playfab/features/pricing/consumption-best-practices). That's the same, regardless of whether the call is in legacy or Azure Functions Cloud Script. If so, your 5.4 GB-s would be right around 42 seconds of total script runtime. But 1 second is time for quite a lot of processing on a server, so apart from deliberate "wait" periods (like calling http.request), many game processes we see in Cloud Script are well under a second. So the 400K/1M GB-s you get with the Standard and Premium accounts is often more sufficient for quite a few game types (Premium would be for when you have a large player population, and so need more resources). If you find that you need much higher server-side compute times per player due to long processing jobs and/or very frequent calls, you may want to consider switching to using hosted game servers, as that may be more economical for your design.

In terms of how often a handler is being hit, if you're using Azure Functions Cloud Script, you can monitor it via the telemetry tools available in Azure (https://docs.microsoft.com/en-us/azure/azure-functions/functions-monitoring?tabs=cmd). For legacy, the API graph on the main dashboard of your title gives you the ability to check on how often Cloud Script execution calls are made, and review any error frequencies, and the Cloud Script (Automation) page shows the breakdown of handlers called in the last 24 hours, along with any errors.