Hi Joran, Thanks for sharing what worked for you.
We do not want to disable the GC entirely. But perhaps we'd like to reduce kMaxNumberOfAttempts constant in Heap::CollectAllAvailableGarbage from 7 to 1 or 2. That still doesn't tackle the original problem of v8 thinking that it's OOM when it's not, and thus running last resort gc. I think we'll continue facing memory allocation problem / gc problem until that is taken care of. Regards, Hitesh. On Thursday, June 6, 2013 2:37:22 PM UTC+5:30, Joran Dirk Greef wrote: > > Hi Hitesh, > > I have had pauses of up to a minute with the GC in V8. > > I fixed it with a fairly oversized hammer: > > 1. Open node/deps/v8/src/heap.cc > 2. Comment out everything inside the "CollectAllAvailableGarbage" function. > 3. Comment out any calls to "CollectGarbage" from within the > "CollectAllGarbage" function. > 4. Recompile Node. > > After that there were no more pauses and the process is not running out of > memory. > > This applies to the V8 bundled with Node v0.8.14, but the main thing is > to neuter the CollectAllGarbage and CollectAllAvailableGarbage functions. > > Hope that helps. > > Joran Greef > -- -- 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.
