I just checked and although I’m on a 4GB variant I see a similar memory usage of ~420M or so. I went back and checked on 5.7.2 and I see a similar level of memory usage their as well. That at least tells me this has been about the same for a while now. Therefore this doesn’t seem specific for the 6.4.0 release.
I see docker/container related processes take up a decent chunk of this used memory. Stopping these processes helps things a bit though there’s still quite a bit of used memory spread through various processes. Also stopping docker kind of defeats the purpose somewhat.
The same build 6.4.0+build.5 for a Verdin iMX8M-Mini has an usage or more or less 200 MB.
Last week I met @stefano.tx and @sergio.tx and it seems that the usage is somehow related to a huva amount of memory reserved by Linux,cma
If this is true, it doesn’t match what is listed here in the Toradex KB.
my application is a Next.js application, which uses Chromium container to render the UI (which is 1080p resolution).
Based on my preliminary profiling, my application requires more or less 650 MB of RAM.
I would like using a QuadLite S0M (which has 1GB of RAM), and I was advised not to create a swap file on the eMMC (see here) to avoid rapid flash degradation.
Hello @henrique.tx
based on my test, it seems that 256MB is the minimum value that allows weston-vivante container running over Torizon OS.
With lower values, weston-vivante crashes.
The other containers that I tested run properly with lower values.
Does weston-vivante require CMA for some reason?
Is it possible that HMP support requires some (unnecessary) big CMA space?
It doesn’t surprise me that weston-vivante needs CMA memory for DMA usage. A quick google search turns up forum posts and such that seem to confirm this. Notably this post from one of the NXP forums.
I don’t have any specific knowledge of the requirements of Weston but it is certainly feasible that there is a minimum amount below which it will fail on an allocation attempt. Do you have any log messages that could confirm that?
Hello @drew.tx ,
I made some tests with the QuadLite 1GB setting 0 as cma memory
Log file attached when vivante crashes, I remove logs of other containers.
For completeness, sometimes everything starts correctly without crashing.
Thanks for that log. I’ve attached it to our internal tickets in case we see other such scenarios. The best I can suggest at the moment is to leave that value at the minimum where it does not crash.