[🐛 Bug]: High level of Workload memory usage

What happened?

Hi all!
I have been trying to deploy selenium grid via helm chart v0.33.0 and noticed high level of workload memory usage.
In this case, azure runs autoscaling and adds a second machine to kubernates when we run tests.

I loaded selenium using kubernates helm chart by changing the following parameters:

• isolateComponents=true (for full services Router, Distributor, EventBus, SessionMap and SessionQueue, ...)
• tls
• 1 node for each browser (chrome, edge, ff)
• INFO log level
• basic authenticator true
• other params by default
• I remove the resource request and limit after deployment(browsers)

kubernates version 1.29.5
chart 0.33.0
selenium images latest

It's probably not a defect, but I need to figure out what's going wrong.
Thanks!

Command used to start Selenium Grid with Docker (or Kubernetes)

helm install selenium-grid docker-selenium/selenium-grid --set isolateComponents=true

Relevant log output

no logs

Operating System

Kebrnates(Azure)

Docker Selenium version (image tag)

latest

Selenium Grid chart version (chart version)

0.33.0

Start by reproducing the documented helm install with isolateComponents=true, the stated Kubernetes, chart, and image versions, and the listed component settings. Inspect memory usage for each resulting workload and compare it with the reported autoscaling behavior; done means identifying an evidence-backed cause or confirming that more diagnostics are needed.