-
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
high memory usage #1913
Comments
According to how to get "real" process memory and environ in Python, we aren't really using as much memory as previously thought. With the debug code added in r19985, we use psutil (docs: https://psutil.readthedocs.io/en/latest/ psutil]) to dump memory info at time intervals:
The "data" memory usage goes up by ~128MB around the time we init websockify and the auth modules / file transfer. |
Helped by r19986, I found that the memory usage is coming from importing websockify. More specifically: websockify imports numpy which is responsible for most of that 128MB memory usage. Follow up ticket: #1926. r19987 changes some of the xpra codec loading code so we don't import numpy unless we really have to (ie: pycuda requires it).
The next big chunks of memory come from the video and csc codecs (~40MB), which is to be expected. And also dbus (20MB!). @maxmylyn: FYI. |
2018-08-01 18:49:00: maxmylyn commented
|
Despite #1861 and #1838, the client and server still use too much memory, even when disabling most of the video and csc modules - or even nuking them from the filesystem.
The text was updated successfully, but these errors were encountered: