Node should not be able to trigger last resort gc.
It can be that recent changes in V8 changed allocation patterns for
Unfortunately it is impossible to figure out what is going on unless
On Mon, Nov 5, 2012 at 7:08 AM, Joran Dirk Greef <jo...@ronomon.com> wrote:
> 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.
>> Contrary to what you might think worst pause time for V8 3.6.x and V8
>> However in 3.6 if you hit a full collection it will always pause your
>> On Mon, Nov 5, 2012 at 1:28 AM, Joran Dirk Greef <jo...@ronomon.com>
>> > V8 126.96.36.199 GC works perfectly.
>> > The one problem now is getting V8 188.8.131.52 to allow max-old-space-size
>> > Is there any way to run V8 184.108.40.206 with max-old-space-size greater than
>> > Or is there a slightly newer version than 220.127.116.11 which allows bigger
>> > Your help would be much appreciated.
>> > --
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.