You can run V8 with --expose-gc. You can then call gc() to manually trigger gc. Don't assume this to be officially supported though.
On Monday, June 13, 2016 at 6:16:23 PM UTC+2, WENZHI CUI wrote: > > Hi Yang, > Thanks very much for the reply. > I have one follow-up question: > Is there any way to change GC activities other than setting heap size? I > don't mind tweaking the source code if options are not exported. > > Thanks, > Wenzhi Cui > > On Monday, June 13, 2016 at 12:43:42 AM UTC-5, Yang Guo wrote: >> >> --gc-interval is a debugging flag and not supposed to be used for >> production. >> >> >> On Saturday, June 11, 2016 at 4:14:15 PM UTC+2, WENZHI CUI wrote: >>> >>> Hi all, >>> Sorry to disturb you all but I have a question regarding tuning GC >>> interval in v8. >>> >>> I am using Node.js v4.2.1 (with Google v8 v4.5.103) as development >>> platform. I want to study the impact of garbage collector on the overall >>> system performance hence I have to run experiments under different GC >>> settings. In specific, I want to change the interval of GC. >>> >>> I tried setting the option "--gc_interval" but it is not working under >>> Release mode (i.e., GC interval is not changed by the option) and will >>> cause a crash under Debug Mode. So I am wondering if this option is no >>> longer supported or there is something wrong with my setup? >>> >>> Also, if you know other effective ways to tune GC activities (options >>> or source code parameters), that will also help my study. Thanks for your >>> time. >>> >>> Yours, >>> Wenzhi Cui >>> >> -- -- 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.
