> On 07 Jun 2013, at 2:04 PM, [email protected] wrote: > Yeah, we serialize and deserialize a lot of data to/from Buffers. I couldn't > spot calls to AdjustAmountOfExternallyAllocatedMemory from node_buffer > though. > Haven't tried running without CollectAllAvailableGarbage. Did neutering that > disable only the last resort gc or entire garbage collection on old > generation for you ?
Neutering CollectAllAvailableGarbage should just disable the 7 times last resort you are seeing. Neutering CollectAllGarbage will eliminate most of the other collection on the old generation. In my case, the collection on old space still runs every now and then but this reduces it. > Also, is there a scenario of facing memory allocation failures when there is > memory available on the machine, but v8 is thinking that it's OOM (and thus > invoking CollectAllAvailableGarbage which doesn't do anything) ? > Regards, > Hitesh. Yes, that is what I had. My machine has 32GB, the process is around 3GB and without those hacks it was spending 50 seconds plus per GC and collecting every 5 seconds. The filesystem had most of the 32GB used as disk cache otherwise nothing else was using it. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
