Chromium optimisation on imx6

[hiten4612]

On my imx6dl custom board, I'm running the chromium-ozone-wayland_75.0.3770.142.bb web browser.

I ran Chrome with the following flags
/usr/lib/chromium/chromium-bin --no-sandbox --reduce-gpu-sandbox --gpu-sandbox-start-early --ignore-gpu-blocklist --enable-gpu-rasterization --enable-features=RawDraw,CanvasOopRasterization,WebRTCPipeWireCapturer --in-process-gpu --use-gl=egl --ozone-platform=wayland

And use the sram command to monitor memory use.
499 0 /usr/lib/chromium/chromium- 0 776.0K 8.1M 25.0M
522 0 /usr/lib/chromium/chromium- 0 6.2M 14.5M 33.8M
538 0 /usr/lib/chromium/chromium- 0 35.6M 48.9M 70.9M
497 0 /usr/lib/chromium/chromium- 0 55.3M 70.4M 97.5M

As was already noted, it uses a lot of RAM. and I'd like to make that memory as small as possible.

[MaxIhlenfeldt]

I'm running the chromium-ozone-wayland_75.0.3770.142.bb web browser

Do I understand correctly that you are running Chromium 75? If so, updating the browser might already give some RAM usage improvements, as I believe they are continuously working on this issue (e.g., in 110 the "Memory Saver" was introduced, which might help with your use case).

[hiten4612]

@MaxIhlenfeldt Thanks for your support, When i run chrome://gpu/ some features use HW Acceleration, while others do not

[MaxIhlenfeldt]

I'm not sure I can help with that a lot, I can only recommend experimenting with the CLI flags you're using to see what effects they have in this regard.

[Rutvij-dev]

Hi @MaxIhlenfeldt,

Any advise on the porting/migration to v110 ?

--
BR

[MaxIhlenfeldt]

I don't recall anything special about 110. If you're facing concrete problems, I'd be happy to try and help. If they're not related to this issue (RAM usage / HW acceleration on imx6), please open a separate issue.

[MaxIhlenfeldt]

I don't think I have any suggestions other than just trying out the newer version. If anything comes up, feel free to open a separate issue.