Hi, On Thu, 16 Mar 2017 12:29:00 +0100 Sebastien Marie <sema...@online.fr> wrote:
> > What did you raise it to? I raised mine to 1536M for both -cur and -max > > and it's had no visible effect. > > Sorry, but 1.5 Go could be a small value currently... Javascript JIT > engine pre-allocate 1 Go for itself at startup, and next the application > needs to do some malloc too... > > You could check the effective current value (datasize-cur) with: > > ksh$ ulimit -d # value in kbytes > 786432 > > Or read the value configured in login.conf: > > $ getcap -f /etc/login.conf -s datasize-cur default staff > default: 768M > staff: 1536M > > For obtain your current login-class: > > $ id -c > default I am currently running with the following and have no problems so far: $ getcap -f /etc/login.conf -s datasize-cur default staff default: 768M staff: 2560MM $ ulimit -d 2621440 $ id -c staff regards Lars
