Received: by 10.66.76.38 with SMTP id h6mr499917paw.15.1343155937151;
        Tue, 24 Jul 2012 11:52:17 -0700 (PDT)
X-BeenThere: v8-users@googlegroups.com
Received: by 10.68.116.103 with SMTP id jv7ls39777pbb.4.gmail; Tue, 24 Jul
 2012 11:52:15 -0700 (PDT)
Received: by 10.68.216.163 with SMTP id or3mr2651539pbc.1.1343155935057;
        Tue, 24 Jul 2012 11:52:15 -0700 (PDT)
Date: Tue, 24 Jul 2012 11:52:14 -0700 (PDT)
From: spollack <s...@pollackphoto.com>
To: v8-users@googlegroups.com
Message-Id: <edc472be-8b2a-41e0-a2f2-b47159b2a1ec@googlegroups.com>
Subject: recommended V8 GC settings for nodejs in heroku (hitting heroku
 memory limits)
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_8_22117619.1343155934017"

------=_Part_8_22117619.1343155934017
Content-Type: multipart/alternative; 
	boundary="----=_Part_9_14832100.1343155934017"

------=_Part_9_14832100.1343155934017
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I am running a nodejs app in heroku, and on certain datasets i'm going over 
the heroku memory limit of 512MB. I'm running node v0.6.6 with defaults. I 
can see via node's process.memoryUsage() that my RSS value does indeed go 
as high as 544MB on my test dataset, and ps shows similar results. 

What V8 GC settings would you recommend in order to keep the RSS lower? 

Are there any known memory behavior improvements of moving to node v0.6.20 
or v0.8.3 that would help me here?

As an aside, running the same test locally (same node version, same code, 
same data) only hits a max RSS of 155MB, almost a factor of 4 different. 
Both are x86_64 machines, although my local machine is OSX Lion (11.4.0 
Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; 
root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64) while heroku is Linux 2.6 
(2.6.32-343-ec2 #45+lp929941v1 SMP Tue Feb 21 14:07:44 UTC 2012 x86_64 
GNU/Linux). Any ideas why that is? 

Thanks.

------=_Part_9_14832100.1343155934017
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I am running a nodejs app in heroku, and on certain datasets i'm going over=
 the heroku memory limit of 512MB. I'm running node v0.6.6 with defaults. I=
 can see via node's process.memoryUsage() that my RSS value does indeed go =
as high as 544MB on my test dataset, and ps shows similar results.&nbsp;<di=
v><br></div><div>What V8 GC settings would you recommend in order to keep t=
he RSS lower?&nbsp;</div><div><br></div><div>Are there any known memory beh=
avior improvements of moving to node v0.6.20 or v0.8.3 that would help me h=
ere?</div><div><br></div><div>As an aside, running the same test locally (s=
ame node version, same code, same data) only hits a max RSS of 155MB, almos=
t a factor of 4 different. Both are x86_64 machines, although my local mach=
ine is OSX Lion (11.4.0 Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PD=
T 2012; root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64) while heroku is Linux 2=
.6 (2.6.32-343-ec2 #45+lp929941v1 SMP Tue Feb 21 14:07:44 UTC 2012 x86_64 G=
NU/Linux). Any ideas why that is?&nbsp;</div><div><br></div><div>Thanks.</d=
iv>
------=_Part_9_14832100.1343155934017--

------=_Part_8_22117619.1343155934017--