Thanks for the --never-compact flag tip. What bad things can I expect using this at run-time? Also, is the compaction step the most expensive operation of mark-sweep-compact algorithm? And how expensive is the flag switching itself?
пятница, 30 октября 2015 г., 10:24:25 UTC+3 пользователь Artem Chivchalov написал: > > Hi all, > > I'm using node.js v5 (V8 4.6.85.25). I wonder is there any way in native > code to explicitly disable GC runs (at least mark-sweep-compact runs) > during the specified period of time, while executing some code sensitive to > delays? Something like this: > > disableGc(); > runCodeWithoutDelays(); > enableGc(); > > Is there an API for that? I'm aware of a possibility to call major GC runs > explicitly, but that triggers non-incremental mark-sweep-compact which is > heavy and takes a much longer time than incremental one. What I'd like to > achieve is just block GC from executing for a while and resume it a bit > later. > -- -- 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/d/optout.
