Test configs to mongodb connection

[jue-henry]

No description provided.

[jue-henry]

Log example for before implementation on dev: https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#logsV2:log-groups/log-group/$252Faws$252Flambda$252Faniml-api-dev-graphql/log-events$3FfilterPattern$3D$2522Connected+to+MongoDB+in+$2522$26start$3D1780939200000$26end$3D1780941599000

[jue-henry]

Results after adding the configs, not seeing much improvement and even potentially worse:
https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#logsV2:log-groups/log-group/$252Faws$252Flambda$252Faniml-api-dev-graphql/log-events$3FfilterPattern$3D$2522Connected+to+MongoDB+in+$2522$26start$3D1780945740000$26end$3D1780946100000

But on mongoDB I am seeing a higher number of connections being made. Does this point toward actual DB slowing down trying to open these connections?

[jue-henry]

Setting maxPoolSize to 1 seems to help a lot:
https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#logsV2:log-groups/log-group/$252Faws$252Flambda$252Faniml-api-dev-graphql/log-events$3FfilterPattern$3D$2522Connected+to+MongoDB+in+$2522$26start$3D1780955400000$26end$3D1780955520000

This is because lambdas do not process more than 1 request at once, and previously the default maxPoolSize of 100 would cause 100 connections to MongoDB on startup