Den 2. jun. 2010 15.14 skrev Chinnu <[email protected]>: > > Thanks again for the reply Erik. > > When you said "unless the VM really is idle of course", does this mean >
What I mean is that if there is real work to do then you shouldn't call the idle notification. If your program is sitting around waiting for input and timers then it should be fine. I suppose it's obvious, but I just thought I'd mention it because although I know nothing about your application I could imagine that aggressively calling the idle notification could cause too many GCs which would hurt performance. We have tried to tune the GC so it invokes itself at suitable intervals without calls to IdleNotification, but of course V8 has no information about IO and timers that the API program may be waiting on. > when we're not invoking any V8 calls (or running any script in V8), or > is it a generally bad practice to use the IdleNotification call? I > gathered from some other posts that this is a way to free allocated > memory within the VM. > > Thanks, > Ravi > > > On Jun 2, 6:02 am, Erik Corry <[email protected]> wrote: > > Den 2. jun. 2010 11.02 skrev Ravi Namballa <[email protected]>: > > > > > Thanks for the reply Eric. > > > > > How about the memory usage? Creating and disposing contexts for each > script > > > seems to allocate more memory, and using IdleNotification() to clear > this > > > has a performance impact. > > > > Yes. The 250us is an average that includes GC overhead I think. Trying > to > > create snapshots with more data in new space and less in the other spaces > > might help here, but I don't expect to have time to look at that. > > > > You shouldn't call IdleNotification unless the VM really is idle of > course. > > > > -- > > Erik Corry > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
