This message was deleted.

Are you caching the feature definitions json?

Yes, with an in-memory database

that should be really fast

It actually is. Just wondering if someone comes up with something better than calling

new GrowthBook()

in every request

There is a

destroy

method you can use at the end of the request to release some memory back. The instances are extremely lightweight. It's technically possible to reuse instances, but usually not worth the complexity.

Thanks both of you for the fast response.