Skip to content
This repository has been archived by the owner on Oct 31, 2019. It is now read-only.

interpreting RAM usage #4

Open
sebastianelsner opened this issue Jan 16, 2015 · 4 comments
Open

interpreting RAM usage #4

sebastianelsner opened this issue Jan 16, 2015 · 4 comments
Labels

Comments

@sebastianelsner
Copy link

I have trouble imtepreting the different RAM fields when querying the /rendernodes resource.

There is systemFreeRam (int), ramSize (int), usedRAM (empty list), freeRam (which never changes)

@sebastianelsner
Copy link
Author

I finally ended up changing the worker code, which reports the ram usage, to use psutls instead of parsing the output of /proc/mem.
If there is interest I can submit a pull request for OpenRenderManagement

@samson-jerome
Copy link
Contributor

ramSize: amount of RAM available on the host (in MB)
systemFreeRam: amount of free memory on the host, evaluated periodically (in MB)
systemSwapPercentage: percentage of swap memory on the host, evaluated periodically (in range [0,1])

the other attributes: usedRAM/freeRam are deprecated. They were introduced when a worker was able to run several commands at a time. This capability was eventually removed because of the lack of confidence on the proper execution of every command and ram use.

@samson-jerome
Copy link
Contributor

Ok for the pull request, it could be interesting to have all "system" calls going through psutils.

@sebastianelsner
Copy link
Author

Using psutils will improve on potential windows compatibility, too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants