Meta tags:

Headings (most frequently used words):

node, js, functions, python, go, java, ruby, php, and, use, of, http, send, an, do, not, start, to, global, cold, initialization, resources, best, practices, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, correctness, tools, performance, write, idempotent, ensure, response, background, activities, always, delete, temporary, files, framework, local, development, error, reporting, manually, exit, sendgrid, emails, avoid, low, concurrency, dependencies, wisely, variables, reuse, objects, in, future, invocations, reduce, starts, by, setting, minimum, number, instances, notes, about, additional, products, pricing, support, engage, example, prewarming, async, library, examples,

Text of the page (most frequently used words):
the (121), #functions (96), cloud (93), and (88), function (85), request (57), http (54), this (49), run (48), using (43), for (42), name (41), google (40), with (40), response (40), from (37), use (36), global (35), cold (34), return (33), import (32), code (30), that (29), can (28), you (28), int (28), your (28), instance (26), start (25), service (25), overview (25), deploy (24), not (23), private (23), time (22), services (22), static (20), context (20), java (19), storage (19), node (18), initialization (18), framework (18), com (18), when (17), variables (17), initialized (17), value (17), flask (17), json (17), best (17), numbers (16), send (15), class (15), object (15), will (15), scope (15), instances (15), environment (15), exit (15), per (14), file (14), lazy (14), called (14), lazyglobal (14), public (14), practices (14), memory (14), string (14), worker (14), system (13), are (13), requests (13), invocation (13), only (13), new (13), should (13), body (13), explicitly (13), python (12), once (12), firestore (12), build (12), jobs (12), pools (12), dependencies (11), computation (11), runs (11), res (11), invocations (11), event (11), driven (11), world (11), hellohttp (11), gpu (11), configure (11), vpc (11), container (11), samples (10), more (10), load (10), client (10), background (10), const (10), execute (10), starts (10), they (10), volumes (10), hello (10), resources (9), sample (9), php (9), variable (9), set (9), ruby (9), error (9), package (9), req (9), require (9), latency (9), during (9), data (9), gson (9), view (9), see (8), also (8), used (8), note (8), may (8), end (8), non_lazy_global (8), lazy_global (8), server (8), stream (8), var (8), example (8), number (8), write (8), local (8), heavycomputation (8), create (8), trigger (8), triggers (8), all (7), thumb (7), other (7), but (7), cache (7), functionsframework (7), task (7), result (7), httprequest (7), err (7), func (7), api (7), text (7), returns (7), functions_framework (7), access (7), minimum (7), application (7), network (7), lightcomputation (7), limits (7), tutorial (7), either (7), implicitly (7), development (7), tools (7), delete (7), logger (7), pub (7), sub (7), maximum (7), about (6), need (6), performance (6), between (6), loading (6), every (6), async (6), must (6), tasks (6), arrays (6), writer (6), printwriter (6), ioexception (6), httpresponse (6), https (6), org (6), httpfunction (6), make_response (6), any (6), into (6), param (6), which (6), block (6), traffic (6), cpu (6), based (6), execution (6), networking (6), functionvar (6), instancevar (6), scopedemo (6), wide (6), process (6), jsonelement (6), migrate (6), agents (6), metrics (6), manage (5), values (5), method (5), on_startup (5), next (5), filewidecomputation (5), functionspecificcomputation (5), non (5), await (5), reduce (5), final (5), default (5), log (5), def (5), module (5), concurrency (5), such (5), first (5), behavior (5), message (5), testing (5), fmt (5), often (5), rack (5), requestjson (5), security (5), migration (5), gpus (5), source (5), job (5), eventarc (5), invoke (5), português (4), español (4), github (4), down (4), information (4), content (4), developers (4), uses (4), set_global (4), declare (4), current (4), sum (4), nonlazyglobal (4), writeasync (4), readonly (4), warning (4), thread (4), safe (4), threading (4), microsoft (4), printf (4), getwriter (4), lazyglobalholder (4), always (4), avoid (4), checks (4), init (4), tips (4), pocoo (4), docs (4), args (4), config (4), library (4), languages (4), could (4), cause (4), low (4), setting (4), connections (4), objects (4), before (4), php_eol (4), computations (4), cachepath (4), compute (4), cached (4), psr (4), serverrequestinterface (4), instance_data (4), make (4), because (4), same (4), instance_var (4), subsequent (4), optimization (4), secure (4), files (4), volume (4), mounts (4), nfs (4), console (4), disk (4), activity (4), after (4), parse (4), escape (4), check (4), field (4), logging (4), requestparsed (4), request_args (4), request_json (4), timeout (4), management (4), containers (4), configuration (4), inference (4), custom (4), identity (4), direct (4), scaling (4), health (4), optimize (4), events (3), started (3), support (3), products (3), understand (3), otherwise (3), its (3), multiple (3), spikes (3), out (3), important (3), different (3), cannot (3), scopes (3), each (3), requestaborted (3), performed (3), there (3), httpcontext (3), handleasync (3), ihttpfunction (3), namespace (3), aspnetcore (3), integer (3), throws (3), void (3), override (3), below (3), declared (3), executes (3), else (3), race (3), conditions (3), implements (3), util (3), nil (3), needed (3), responsewriter (3), lazily (3), net (3), turned (3), get (3), document (3), order (3), ensure (3), pool (3), true (3), type (3), main (3), following (3), times (3), recommend (3), initialize (3), language (3), long (3), ensures (3), complete (3), especially (3), being (3), caching (3), has (3), what (3), modules (3), how (3), serve (3), expensive (3), sending (3), executions (3), read (3), operations (3), deployment (3), way (3), future (3), known (3), individual (3), section (3), describes (3), test (3), version (3), usage (3), asynchronous (3), parameter (3), _logger (3), nameelement (3), null (3), html (3), guides (3), hosting (3), frameworks (3), monitoring (3), solutions (3), distributed (3), databases (3), introduction (3), web (3), mcp (3), authenticate (3), connectors (3), host (3), cost (3), autoscale (3), labels (3), secrets (3), ephemeral (3), cifs (3), smb (3), entrypoint (3), retries (3), connect (3), concurrent (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), our (2), third (2), terms (2), site (2), youtube (2), center (2), status (2), notes (2), pricing (2), hard (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), under (2), license (2), feedback (2), making (2), handle (2), find (2), optimizing (2), video (2), additional (2), particularly (2), define (2), several (2), preserve (2), above (2), _request (2), function_specific_computation (2), file_wide_computation (2), aggregate (2), might (2), some (2), lazyfields (2), linq (2), getasint (2), getinstance (2), constructor (2), newclient (2), pre (2), clientonce (2), add (2), sync (2), googlecloudplatform (2), writing (2), globals (2), examples (2), collection (2), synchronous (2), required (2), take (2), min_instances (2), longer (2), libraries (2), asynchronously (2), running (2), issues (2), described (2), served (2), until (2), able (2), sensitive (2), completing (2), doesn (2), however (2), impact (2), keep (2), possible (2), happens (2), without (2), would (2), incurring (2), incoming (2), perform (2), lock_ex (2), empty (2), locking (2), prevent (2), flock (2), txt (2), their (2), them (2), runtime (2), does (2), heavy (2), invocation_data (2), my_instance_data (2), retrieve (2), call (2), key (2), built (2), practice (2), executed (2), instead (2), top (2), level (2), usually (2), globalvariable (2), functionvariable (2), calling (2), fprintf (2), locally (2), function_var (2), light_computation (2), declares (2), heavy_computation (2), placeholder (2), significant (2), across (2), previous (2), reuse (2), stateless (2), scratch (2), occurs (2), existing (2), allow (2), outbound (2), port (2), emails (2), email (2), engine (2), sendgrid (2), manually (2), unexpected (2), specific (2), throw (2), reporting (2), provides (2), dependency (2), available (2), include (2), lock (2), requirements (2), processing (2), through (2), temporary (2), sometimes (2), failing (2), lead (2), logs (2), anything (2), errors (2), promise (2), completion (2), sprintf (2), querystring (2), deploying (2), register (2), cgi (2), hello_http (2), parsing (2), parseexception (2), catch (2), try (2), reader (2), query (2), url (2), parameters (2), ilogger (2), jsonparseexception (2), jsonobject (2), fprint (2), helloworld (2), palletsprojects (2), escapehtml (2), unpredictable (2), part (2), general (2), designing (2), implementing (2), unnecessary (2), documentation (2), sdk (2), infrastructure (2), costs (2), observability (2), industry (2), hybrid (2), multicloud (2), analytics (2), pipelines (2), troubleshoot (2), oci (2), app (2), assisted (2), llm (2), remote (2), adk (2), a2a (2), prometheus (2), projects (2), controls (2), shared (2), connector (2), automate (2), workflows (2), external (2), description (2), metadata (2), systems (2), capacity (2), rollbacks (2), revisions (2), continuous (2), tags (2), integrate (2), image (2), workflow (2), base (2), runtimes (2), images (2), configurations (2), serving (2), git (2), results (2), plan (2), prepare (2), gcloud (2), develop (2), cases (2), cross (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, release, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hardtounderstand, incorrect, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, page, details, registered, trademark, oracle, affiliates, policies, apache, creative, commons, attribution, helps, defer, easier, atlas, boot, technique, importing, albeit, expense, readability, single, unless, waste, never, non_lazy, tips_lazy, others, don, necessary, complex, paths, executionandpublication, lazythreadsafetymode, needs, getlazyglobal, prohibits, instantiation, wikipedia, wiki, demand_holder_idiom, demand, holder, idiom, introduce, servlet, classes, statusinternalservererror, internal, shadowing, wish, initializing, contains, noqa, f824, lazy_globals, none, lazyglobals, let, lower, something, now, preloaded, fetch, doc, comes, warm, connection, preload, preferrest, tla, means, es6, extension, adding, mjs, advantage, completes, blocking, prewarming, chose, high, better, depending, two, behaviors, combination, immediately, causing, continue, hand, issue, configured, min, scenario, useful, minimize, thereby, higher, learn, scales, change, ready, reduces, references, outside, duration, store, _lightcomputation, lighter, file_put_contents, _heavycomputation, computing, lock_un, stream_get_contents, fopen, reading, file_exists, sys_get_temp_dir, cached_value, packagist, providers, implementation, typically, fast, writable, directories, computed, perform_light_computation, tips_scopes, difficult, isolate, toplevel, pair, pass, perform_heavy_computation, actual, starting, verify, whereas, invoked, benefit, have, one, created, scoped, globally, scope_demo, todo, developer, own, recreate, moving, improvements, creates, shares, reaching, given, guarantee, state, preserved, recycles, reused, having, recomputed, those, well, correctly, evaluated, wisely, efficiency, increases, reduced, hold, increasing, recently, spike, great, limiting, leveraged, therefore, smtp, recommended, party, options, die, abort, sys, 200, exiting, please, idioms, exception, handling, uncaught, exceptions, force, takes, bit, faster, guidelines, implement, interact, listed, automatically, added, latest, preferred, relevant, installed, consistently, environments, manager, pin, larger, pipelining, creating, passing, output, directly, term, consider, selecting, choosing, plot, list, directory, filesystem, consume, persist, these, eventually, detected, finding, logged, line, saying, finished, buried, deeper, callbacks, timers, present, review, sure, finish, terminate, addition, resumes, interfering, diagnose, accessing, terminates, leads, reset, econnreset, settled, terminating, terminated, finishes, signals, argument, graceful, termination, progress, callback, activities, htmlspecialchars, getqueryparams, json_last_error_msg, runtimeexception, json_last_error, json_error_none, json_decode, getbody, getcontents, match, function_target, enables, omitting, functions_signature_type, cloudfunctions, escape_html, hash, encoded, array, standarderror, rescue, rewind, begin, params, www, rubydoc, info, gems, logerror, jsonexception, getstring, jsonvaluekind, valuekind, trygetproperty, deserialize, jsonserializer, length, readtoendasync, streamreader, textreader, extensions, getmessage, severe, getasstring, getasjsonobject, isjsonobject, getreader, fromjson, orelse, getfirstqueryparameter, getname, getlogger, escapestring, decode, newdecoder, struct, encoding, elif, silent, get_json, markupsafe, header, responds, parsed, according, remember, shown, executing, charged, entire, resulting, timeouts, triggered, produce, even, lets, retry, fails, retrying, idempotent, correctness, recommendations, around, amounts, streamline, whatever, extent, avoiding, save, categorize, preferences, stay, organized, collections, home, troubleshooting, gke, kubernetes, vmware, tanzu, spring, music, choose, compliant, strategy, foundry, heroku, aws, lambda, 1st, gen, cookbook, vibe, coding, accelerated, transcoding, ffmpeg, batch, fine, tune, llms, hugging, face, transformers, opencv, acceleration, gemma, models, ollama, browser, automation, servers, n8n, explore, tracing, audit, opentelemetry, monitor, multi, tenant, platforms, untrusted, software, supply, chain, insights, constraints, customer, managed, encryption, keys, threat, detection, binary, authorization, protect, armor, iap, control, iam, user, authentication, users, audiences, design, mesh, restrict, endpoint, ingress, address, project, standard, dual, stack, ipv4, ipv6, ips, dns, pull, subscriptions, runners, kafka, autoscaler, scale, count, splits, work, checkpoints, stop, parallelism, scheduled, zonal, redundancy, grpc, database, routed, entries, push, subscription, series, schedule, websocket, chat, websockets, webhook, target, account, automatic, updates, supported, manual, autoscaling, sandboxes, recommender, billing, gradual, rollouts, copy, frontend, proxying, nginx, enable, session, affinity, failover, regions, assets, cdn, mapping, domains, compose, sources, codelabs, spanner, bigquery, tutorials, compare, commands, within, install, containerize, shell, sveltekit, nuxt, angular, ssr, kotlin, agent, kit, streamlit, smolagents, langchain, gradio, fastapi, repository, good, fit, contract, resource, model, discover, free, skip,

Text of the page (random words):
son jsonserializer deserialize jsonelement text if json trygetproperty name out jsonelement nameelement nameelement valuekind jsonvaluekind string name nameelement getstring catch jsonexception parseexception _logger logerror parseexception error parsing json request await context response writeasync hello name context requestaborted ruby require functions_framework require cgi escape require json functionsframework http hello_http do request the request parameter is a rack request object see https www rubydoc info gems rack rack request name request params name begin request body rewind json parse request body read name rescue standarderror nil end world return the response body as a string you can also return a rack response object a rack response array or a hash which will be json encoded into a response hello cgi escape_html name end php php use google cloudfunctions functionsframework use psr http message serverrequestinterface register the function with functions framework this enables omitting the functions_signature_type http environment variable when deploying the function_target environment variable should match the first parameter functionsframework http hellohttp hellohttp function hellohttp serverrequestinterface request string name world body request getbody getcontents if empty body json json_decode body true if json_last_error json_error_none throw new runtimeexception sprintf could not parse body s json_last_error_msg name json name name querystring request getqueryparams name querystring name name return sprintf hello s htmlspecialchars name do not start background activities background activity is anything that happens after your function has terminated a function invocation finishes once the function returns or otherwise signals completion such as by calling the callback argument in node js event driven functions any code run after graceful termination cannot access the cpu and will not make any progress note if a node js event driven function returns a promise cloud run functions ensures that the promise is settled before terminating in addition when a subsequent invocation is executed in the same environment your background activity resumes interfering with the new invocation this may lead to unexpected behavior and errors that are hard to diagnose accessing the network after a function terminates usually leads to connections being reset econnreset error code background activity can often be detected in logs from individual invocations by finding anything that is logged after the line saying that the invocation finished background activity can sometimes be buried deeper in the code especially when asynchronous operations such as callbacks or timers are present review your code to make sure all asynchronous operations finish before you terminate the function always delete temporary files local disk storage in the temporary directory is an in memory filesystem files that you write consume memory available to your function and sometimes persist between invocations failing to explicitly delete these files may eventually lead to an out of memory error and a subsequent cold start you can see the memory used by an individual function by selecting it in the list of functions in the google cloud console and choosing the memory usage plot if you need access to long term storage consider using cloud run volume mounts with cloud storage or nfs volumes you can reduce memory requirements when processing larger files using pipelining for example you can process a file on cloud storage by creating a read stream passing it through a stream based process and writing the output stream directly to cloud storage functions framework to ensure that the same dependencies are installed consistently across environments we recommend that you include the functions framework library in your package manager and pin the dependency to a specific version of functions framework to do this include your preferred version in the relevant lock file for example package lock json for node js or requirements txt for python if functions framework is not explicitly listed as a dependency it will automatically be added during the build process using the latest available version tools this section provides guidelines on how to use tools to implement test and interact with cloud run functions local development function deployment takes a bit of time so it is often faster to test the code of your function locally developers can use the functions framework for local testing error reporting in languages that use exception handling do not throw uncaught exceptions because they force cold starts in future invocations do not manually exit manually exiting can cause unexpected behavior please use the following language specific idioms instead node js do not use process exit http functions should send a response with res status 200 send message and event driven functions will exit once they return either implicitly or explicitly python do not use sys exit http functions should explicitly return a response as a string and event driven functions will exit once they return a value either implicitly or explicitly go do not use os exit http functions should explicitly return a response as a string and event driven functions will exit once they return a value either implicitly or explicitly java do not use system exit http functions should send a response with response getwriter write message and event driven functions will exit once they return either implicitly or explicitly c do not use system environment exit http functions should send a response with context response writeasync message and event driven functions will exit once they return either implicitly or explicitly ruby do not use exit or abort http functions should explicitly return a response as a string and event driven functions will exit once they return a value either implicitly or explicitly php do not use exit or die http functions should explicitly return a response as a string and event driven functions will exit once they return a value either implicitly or explicitly use sendgrid to send emails cloud run functions does not allow outbound connections on port 25 so you cannot make non secure connections to an smtp server the recommended way to send emails is to use a third party service such as sendgrid you can find other options for sending email in the sending email from an instance tutorial for google compute engine performance this section describes best practices for optimizing performance avoid low concurrency because cold starts are expensive being able to reuse recently started instances during a spike is a great optimization to handle load limiting concurrency limits how existing instances can be leveraged therefore incurring more cold starts increasing concurrency helps defer multiple requests per instance making spikes of load easier to handle note as efficiency increases and their required number is reduced individual function instances may use more memory to hold requests and require more cpu to process them use dependencies wisely because functions are stateless the execution environment is often initialized from scratch during what is known as a cold start when a cold start occurs the global context of the function is evaluated if your functions import modules the load time for those modules can add to the invocation latency during a cold start you can reduce this latency as well as the time needed to deploy your function by loading dependencies correctly and not loading dependencies your function doesn t use use global variables to reuse objects in future invocations there is no guarantee that the state of a cloud run function will be preserved for future invocations however cloud run functions often recycles the execution environment of a previous invocation if you declare a variable in global scope its value can be reused in subsequent invocations without having to be recomputed this way you can cache objects that may be expensive to recreate on each function invocation moving such objects from the function body to global scope may result in significant performance improvements the following example creates a heavy object only once per function instance and shares it across all function invocations reaching the given instance node js const functions require google cloud functions framework todo developer define your own computations const lightcomputation heavycomputation require computations global instance wide scope this computation runs once at instance cold start const instancevar heavycomputation http function that declares a variable param object req request context param object res response context functions http scopedemo req res per function scope this computation runs every time this function is called const functionvar lightcomputation res send per instance instancevar per function functionvar python import time import functions_framework placeholder def heavy_computation return time time placeholder def light_computation return time time global instance wide scope this computation runs at instance cold start instance_var heavy_computation functions_framework http def scope_demo request http cloud function that declares a variable args request flask request the request object http flask pocoo org docs 1 0 api flask request returns the response text or any set of values that can be turned into a response object using make_response http flask pocoo org docs 1 0 api flask flask make_response per function scope this computation runs every time this function is called function_var light_computation return f instance instance_var function function_var go h is in the global instance wide scope var h string init runs during package initialization so this will only run during an an instance s cold start func init h heavycomputation functions http scopedemo scopedemo scopedemo is an example of using globally and locally scoped variables in a function func scopedemo w http responsewriter r http request l lightcomputation fmt fprintf w global q local q h l java import com google cloud functions httpfunction import com google cloud functions httprequest import com google cloud functions httpresponse import java io ioexception import java io printwriter import java util arrays public class scopes implements httpfunction global instance wide scope this computation runs at instance cold start warning class variables used in functions code must be thread safe private static final int instance_var heavycomputation override public void service httprequest request httpresponse response throws ioexception per function scope this computation runs every time this function is called int functionvar lightcomputation var writer new printwriter response getwriter writer printf instance s function s instance_var functionvar private static int lightcomputation int numbers new int 1 2 3 4 5 6 7 8 9 return arrays stream numbers sum private static int heavycomputation int numbers new int 1 2 3 4 5 6 7 8 9 return arrays stream numbers reduce t x t x getasint c using google cloud functions framework using microsoft aspnetcore http using system linq using system threading tasks namespace scopes public class function ihttpfunction global server wide scope this computation runs at server cold start warning class variables used in functions code must be thread safe private static readonly int globalvariable heavycomputation note that one instance of this class function is created per invocation so calling heavycomputation in the constructor would not have the same benefit public async task handleasync httpcontext context per function invocation scope this computation runs every time this function is called int functionvariable lightcomputation await context response writeasync global globalvariable function functionvariable context requestaborted private static int lightcomputation int numbers 1 2 3 4 5 6 7 8 9 return numbers sum private static int heavycomputation int numbers 1 2 3 4 5 6 7 8 9 return numbers aggregate current next current next ruby global instance wide scope this block runs on cold start before any function is invoked note it is usually best to run global initialization in an on_startup block instead at the top level of the ruby file this is because top level code could be executed to verify the function during deployment whereas an on_startup block is run only when an actual function instance is starting up functionsframework on_startup do instance_data perform_heavy_computation to pass data into function invocations the best practice is to set a key value pair using the ruby function framework s built in set_global method functions can call the global method to retrieve the data by key you can also use ruby global variables or toplevel local variables but they can make it difficult to isolate global data for testing set_global my_instance_data instance_data end functionsframework http tips_scopes do _request per function scope this method is called every time this function is called invocation_data perform_light_computation retrieve the data computed by the on_startup block instance_data global my_instance_data instance instance_data function invocation_data end php use psr http message serverrequestinterface function scopedemo serverrequestinterface request string heavy computations should be cached between invocations the php runtime does not preserve variables between invocations so we must write their values to a file or otherwise cache them all writable directories in cloud functions are in memory so file based caching operations are typically fast you can also use psr 6 caching libraries for this task https packagist org providers psr cache implementation cachepath sys_get_temp_dir cached_value txt response if file_exists cachepath read cached value from file using file locking to prevent race conditions between function executions response reading cached value php_eol fh fopen cachepath r flock fh lock_ex instancevar stream_get_contents fh flock fh lock_un else compute cached value write to file using file locking to prevent race conditions between function executions response cache empty computing value php_eol instancevar _heavycomputation file_put_contents cachepath instancevar lock_ex lighter computations can re run on each function invocation functionvar _lightcomputation response per instance instancevar php_eol response per function functionvar php_eol return response it is particularly important to cache network connections library references and api client objects in global scope see networking best practices for examples note background tasks should not be performed outside of the duration of a request if you need to initialize a global variable with the result from an expensive background task perform the task during your function s execution and store its result before sending a response reduce cold starts by setting a minimum number of instances b...