Cloud Functions pricing in GCP - Commands & Configuration

Introduction

Cloud Functions pricing helps you understand how much you pay when your small pieces of code run in the cloud. It solves the problem of knowing your costs based on how often and how long your code runs.

When you want to know how much your serverless functions cost after running them.

When you need to estimate your monthly bill based on function usage.

When you want to control costs by understanding what affects pricing.

When you want to compare costs between different cloud providers.

When you plan to optimize your functions to reduce expenses.

Commands

This command shows details about your deployed Cloud Function, including its configuration and usage metrics that affect pricing.

Terminal

gcloud functions describe example-function --region=us-central1

Expected Output

name: projects/my-project/locations/us-central1/functions/example-function

status: ACTIVE

entryPoint: helloWorld

runtime: nodejs18

availableMemoryMb: 256

timeout: 60s

httpsTrigger:

  url: https://us-central1-my-project.cloudfunctions.net/example-function

sourceUploadUrl: https://storage.googleapis.com/gcf-upload-us-central1/...

updateTime: '2024-06-01T12:00:00Z'

versionId: '1'

→

--region - Specifies the region where the function is deployed.

This command fetches the last 5 log entries for your function to help you see how often it runs and if there are any errors affecting cost.

Terminal

gcloud functions logs read example-function --limit=5 --region=us-central1

Expected Output

2024-06-01 12:01:00 example-function: Function execution started

2024-06-01 12:01:01 example-function: Function execution finished

2024-06-01 12:02:00 example-function: Function execution started

2024-06-01 12:02:01 example-function: Function execution finished

2024-06-01 12:03:00 example-function: Function execution started

→

--limit - Limits the number of log entries returned.

→

--region - Specifies the region of the function.

This command lists your billing budgets to help you monitor and control your Cloud Functions spending.

Terminal

gcloud billing budgets list

Expected Output

NAME                AMOUNT  FILTERS

monthly-budget      100.00  service=cloudfunctions.googleapis.com

Key Concept

If you remember nothing else from this pattern, remember: Cloud Functions pricing depends mainly on how many times your function runs, how long it runs, and how much memory it uses.

Common Mistakes

Ignoring the function's memory size when estimating costs.

Memory size affects the price per 100ms of execution, so ignoring it leads to wrong cost estimates.

Always check and include the memory allocation of your function when calculating pricing.

Not considering the number of invocations in cost calculations.

Each function call counts as an invocation and adds to the cost, so missing this leads to underestimating expenses.

Count all invocations when estimating your monthly cost.

Assuming free tier covers all usage.

Free tier has limits; exceeding them results in charges.

Track your usage to know when you go beyond the free tier.

Summary

Use 'gcloud functions describe' to see function details affecting pricing.

Check function logs to understand invocation frequency and errors.

Use billing budgets to monitor and control your Cloud Functions costs.