[Feature Request]: Configure max Chrome processes per container

[anthonysterling]

What needs to be done?

I'm deploying the published docker container to kubernetes and I'd like to be able to limit the number of Chrome processes that are spawned.

What problem does this solve?

During some capacity planning, load testing the deployment resulted in unbounded Chrome processes being spawned eventually resulting in the container being killed due to memory exhastion.

Target users/beneficiaries

No response

Current alternatives/workarounds

We could leverage the auto-scaling properties of kubernetes, but provisioning the additional workload capacity can take a little while and is reactionary.

Proposed approach

I'd like a config option that, when configured, limits the numebr of Chrome process to that number in the container. If the number of processes is already at max, the HTTP API should return 429 Too Many Requests. This would ensure the reliablity of the current deployment and a signal to adjust that tunable and/or replica counts.