Question: After stoping Galaxy (via Docker) large RAM buffer/cache remains used on machine?
0
gravatar for vebaev
3.3 years ago by
vebaev • 130
vebaev • 130 wrote:

Hi,

 

I see a lot memory used after running Galaxy and than stopping it (stoping docker container):

free -h
              total        used        free      shared  buff/cache   available
Mem:           125G        885M         82G        8.7M         42G        124G
Swap:           15G          0B         15G

Is that normal 42GB stays cached and not freed? Also I see also some python processes remaining even the Galaxy container is stopped?

 

 1150 root       20   0  537M 16696  5664 S  0.0  0.0  0:21.48 /usr/bin/python -Es /usr/sbin/tuned -l -P
 1193 root       20   0  537M 16696  5664 S  0.0  0.0  0:00.00 /usr/bin/python -Es /usr/sbin/tuned -l -P
 1195 root       20   0  537M 16696  5664 S  0.0  0.0  0:00.00 /usr/bin/python -Es /usr/sbin/tuned -l -P
 1197 root       20   0  537M 16696  5664 S  0.0  0.0  0:01.20 /usr/bin/python -Es /usr/sbin/tuned -l -P
 1264 root       20   0  512M 10760  6508 S  0.0  0.0  0:08.33 /usr/sbin/NetworkManager --no-daemon
 1290 root       20   0  512M 10760  6508 S  0.0  0.0  0:00.36 /usr/sbin/NetworkManager --no-daemon
 1284 root       20   0  512M 10760  6508 S  0.0  0.0  0:00.00 /usr/sbin/NetworkManager --no-daemon
 1291 root       20   0  512M 10760  6508 S  0.0  0.0  0:00.05 /usr/sbin/NetworkManager --no-daemon
 1334 polkitd    20   0  502M 10220  4560 S  0.0  0.0  0:00.33 /usr/lib/polkit-1/polkitd --no-debug
 1319 polkitd    20   0  502M 10220  4560 S  0.0  0.0  0:00.70 /usr/lib/polkit-1/polkitd --no-debug
 1331 polkitd    20   0  502M 10220  4560 S  0.0  0.0  0:00.00 /usr/lib/polkit-1/polkitd --no-debug
 1336 polkitd    20   0  502M 10220  4560 S  0.0  0.0  0:00.00 /usr/lib/polkit-1/polkitd --no-debug
 1337 polkitd    20   0  502M 10220  4560 S  0.0  0.0  0:00.00 /usr/lib/polkit-1/polkitd --no-debug
 1341 polkitd    20   0  502M 10220  4560 S  0.0  0.0  0:00.00 /usr/lib/polkit-1/polkitd --no-debug
47419 root       20   0  408M 13416  8220 S  0.5  0.0  0:17.46 /usr/bin/docker -d -H fd://
47420 root       20   0  408M 13416  8220 S  0.0  0.0  0:02.04 /usr/bin/docker -d -H fd://
47421 root       20   0  408M 13416  8220 S  0.0  0.0  0:00.00 /usr/bin/docker -d -H fd://
47422 root       20   0  408M 13416  8220 S  0.0  0.0  0:00.77 /usr/bin/docker -d -H fd://
47423 root       20   0  408M 13416  8220 S  0.0  0.0  0:07.12 /usr/bin/docker -d -H fd://
47435 root       20   0  408M 13416  8220 S  0.0  0.0  0:03.16 /usr/bin/docker -d -H fd://​

 

docker ram • 833 views
ADD COMMENT • link • modified 3.1 years ago by Jennifer Hillman Jackson ♦ 25k • written 3.3 years ago by vebaev • 130
2
gravatar for Bjoern Gruening
3.3 years ago by
Bjoern Gruening ♦ 5.1k
Germany
Bjoern Gruening ♦ 5.1k wrote:

I can be wrong, but the cache is freed as soon as something else needs to access it. So this is nothing to be worried about. If this is a bug, it's a Docker bug and you should ask the Docker help desk. Moreover, the remaining python processes are not Galaxy related. I'm not aware of any way that a process started in Docker can run without Docker. So everything will be gone after you stop your container. Anything else is a Docker bug, I assume and not a Galaxy one.

ADD COMMENT • link written 3.3 years ago by Bjoern Gruening ♦ 5.1k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 177 users visited in the last hour