Received: by 10.58.246.37 with SMTP id xt5mr3291149vec.13.1352128108396;
Mon, 05 Nov 2012 07:08:28 -0800 (PST)
X-BeenThere: v8-users@googlegroups.com
Received: by 10.52.20.7 with SMTP id j7ls5320865vde.0.gmail; Mon, 05 Nov 2012
07:08:26 -0800 (PST)
Received: by 10.52.96.71 with SMTP id dq7mr1375660vdb.11.1352128106019;
Mon, 05 Nov 2012 07:08:26 -0800 (PST)
Date: Mon, 5 Nov 2012 07:08:25 -0800 (PST)
From: Joran Dirk Greef <jo...@ronomon.com>
To: v8-users@googlegroups.com
Message-Id: <33fa9682-e7b8-421d-aded-f835b36a4a86@googlegroups.com>
In-Reply-To: <CAPD5VRvCwo+Z9S2Mtxbr6Rmz5=U4UbrZ3WCV-U89Y6aN71=-+w@mail.gmail.com>
References: <0502d618-7cdd-46f2-8ec6-72b54e0b440d@googlegroups.com>
<CAPD5VRvCwo+Z9S2Mtxbr6Rmz5=U4UbrZ3WCV-U89Y6aN71=-+w@mail.gmail.com>
Subject: Re: [v8-users] V8 3.6.6.25 with max-old-space-size greater than
1900MB?
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_108_22818740.1352128105716"
------=_Part_108_22818740.1352128105716
Content-Type: multipart/alternative;
boundary="----=_Part_109_20963969.1352128105716"
------=_Part_109_20963969.1352128105716
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
In practice it's working perfectly now. I rolled Node from v0.8 back to
v0.6 and the false positive allocation errors are no longer happening.
There's no more "last resort gc". Load has dropped from 100% to 1%. The gc
trace looks normal now. I assumed the GC errors were due to the different
version of V8 bundled with Node. Perhaps it's something in Node triggering
full GC repetitively? Would Node trigger GC by itself?
On Monday, November 5, 2012 4:53:59 PM UTC+2, Vyacheslav Egorov wrote:
>
> > Recent GC changes are unable to handle millions of long-lived entities.
> V8 3.6.6.25 GC works perfectly.
>
> Contrary to what you might think worst pause time for V8 3.6.x and V8
> 3.7 - 3.15 should be roughly the same. V8 3.7 will also do 7 GCs in a
> row as a last resort.
>
> However in 3.6 if you hit a full collection it will always pause your
> app for much longer then a incremental collector of 3.7 and later
> would (given that everything is tweaked correctly).
>
> --
> Vyacheslav Egorov
>
>
> On Mon, Nov 5, 2012 at 1:28 AM, Joran Dirk Greef <jo...@ronomon.com<javascript:>>
> wrote:
> > Recent GC changes in V8 are wreaking havoc with a production app. GC
> traces
> > are showing pauses of over 22 seconds. Recent GC changes are unable to
> > handle millions of long-lived entities.
> >
> > V8 3.6.6.25 GC works perfectly.
> >
> > The one problem now is getting V8 3.6.6.25 to allow max-old-space-size
> > greater than 1900 MB on Ubuntu.
> >
> > Is there any way to run V8 3.6.6.25 with max-old-space-size greater than
> > 1900 MB?
> >
> > Or is there a slightly newer version than 3.6.6.25 which allows bigger
> heaps
> > but without all the new GC work?
> >
> > Your help would be much appreciated.
> >
> > --
> > v8-users mailing list
> > v8-u...@googlegroups.com <javascript:>
> > http://groups.google.com/group/v8-users
>
------=_Part_109_20963969.1352128105716
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
In practice it's working perfectly now. I rolled Node from v0.8 back to v0.6 and the false positive allocation errors are no longer happening. There's no more "last resort gc". Load has dropped from 100% to 1%. The gc trace looks normal now. I assumed the GC errors were due to the different version of V8 bundled with Node. Perhaps it's something in Node triggering full GC repetitively? Would Node trigger GC by itself?<br><br>On Monday, November 5, 2012 4:53:59 PM UTC+2, Vyacheslav Egorov wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">> Recent GC changes are unable to handle millions of long-lived entities. V8 3.6.6.25 GC works perfectly.
<br>
<br>Contrary to what you might think worst pause time for V8 3.6.x and V8
<br>3.7 - 3.15 should be roughly the same. V8 3.7 will also do 7 GCs in a
<br>row as a last resort.
<br>
<br>However in 3.6 if you hit a full collection it will always pause your
<br>app for much longer then a incremental collector of 3.7 and later
<br>would (given that everything is tweaked correctly).
<br>
<br>--
<br>Vyacheslav Egorov
<br>
<br>
<br>On Mon, Nov 5, 2012 at 1:28 AM, Joran Dirk Greef <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="bZ95lompoAcJ">jo...@ronomon.com</a>> wrote:
<br>> Recent GC changes in V8 are wreaking havoc with a production app. GC traces
<br>> are showing pauses of over 22 seconds. Recent GC changes are unable to
<br>> handle millions of long-lived entities.
<br>>
<br>> V8 3.6.6.25 GC works perfectly.
<br>>
<br>> The one problem now is getting V8 3.6.6.25 to allow max-old-space-size
<br>> greater than 1900 MB on Ubuntu.
<br>>
<br>> Is there any way to run V8 3.6.6.25 with max-old-space-size greater than
<br>> 1900 MB?
<br>>
<br>> Or is there a slightly newer version than 3.6.6.25 which allows bigger heaps
<br>> but without all the new GC work?
<br>>
<br>> Your help would be much appreciated.
<br>>
<br>> --
<br>> v8-users mailing list
<br>> <a href="javascript:" target="_blank" gdf-obfuscated-mailto="bZ95lompoAcJ">v8-u...@googlegroups.com</a>
<br>> <a href="http://groups.google.com/group/v8-users" target="_blank">http://groups.google.com/<wbr>group/v8-users</a>
<br></blockquote>
------=_Part_109_20963969.1352128105716--
------=_Part_108_22818740.1352128105716--
Message from discussion V8 3.6.6.25 with max-old-space-size greater than 1900MB?
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2013 Google |