This message was deleted.

I would still create a separate GrowthBook instance for every invocation. The SDK will cache the features in memory and reuse them across instances. Most serverless runtimes will reuse the environment for many requests so the cost of fetching should only be incurred once as part of cold starts.