How can I configure always-ready instances in the Flex Consumption plan to minimize cost for a low-traffic .NET function app?

For a low-traffic .NET Azure Functions app, I want to keep execution costs low while maintaining acceptable start‑up latency. The Flex Consumption plan offers optional always‑ready instances that can reduce cold starts, but they incur a baseline memory charge when idle. I am uncertain about the trade‑off between this baseline cost and the pay‑per‑execution savings of scaling from zero, and how many always‑ready instances are appropriate for my workload.

How does the baseline memory cost of always‑ready instances compare to the pay‑per‑execution cost of scaling from zero for a low‑traffic .NET function? What is the recommended number of always‑ready instances to balance cost and latency for a workload with a given execution frequency? How can I monitor and adjust always‑ready settings to avoid over‑provisioning while meeting latency SLAs?