This question already has an answer here:

I have a program in python which takes lots of ram. My server has 16gb of ram, but when the program reaches ~8gb of ram, the os starts writing on disk which breaks performance.

I want the process I'm running to use all the available RAM. Why does it seem limited?

I'm running a pure debian os.

    debian@lti-status:~/tests$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 64119
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 64119
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

marked as duplicate by Rui F Ribeiro debian Mar 22 at 21:20

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • The situation I had was very similar. Disk IO caused the kernel to try to expand it's disk cache and triggered the kernel to swap application memory to disk. You can try the solutions linked above or simply remove SWAP for a short space of time. – Philip Couling Mar 22 at 12:10

Browse other questions tagged or ask your own question.