Re: [v8-users] proto in dictionary

JavaScript objects must always have a prototype. Internal implementation details like how the properties are stored can't influence that. On Fri, Sep 18, 2015 at 12:57 PM, dmonji wrote: > I understand that when too many properties are added or a property is > deleted

[v8-users] proto in dictionary

I understand that when too many properties are added or a property is deleted from the object, object representation changes to slow(dictionary) mode. In this case, does proto property still exist? If not, how is inheritance handled in case of dictionary object representation? -- -- v8-users

[v8-users] prooto in dictionary

I understand that when too many properties are added or a property is deleted from the object, object representation changes to slow(dictionary) mode. In this case, does proto property still exist? If not, how is inheritance handled in case of dictionary object representation? -- -- v8-users

Re: [v8-users] Property access time in JavaScript programs

Is there any way to measure it? I tried to instrument the JavaScript code, and summed up the time between "before access" and "after access". But I am not very sure if this is the right way to measure the time required for property accesses. Any thoughts on this? On Friday, 18 September 2015

Re: [v8-users] Property access time in JavaScript programs

Property access time is not measured separately. On Fri, Sep 18, 2015 at 12:56 PM, dmonji wrote: > I want to compute the proportion of time spent on property accesses in > JavaScript programs. I am aware of >

[v8-users] Property access time in JavaScript programs

I want to compute the proportion of time spent on property accesses in JavaScript programs. I am aware of code.com/svn/branches/bleeding_edge/tools/profviz/profviz.html which is a cpu profiler. But it is not clear what exactly does "execution" refer to since "ic cache"

Re: [v8-users] Property access time in JavaScript programs

I don't think it's possible to measure property access times directly. One reason is that a single property access is much, much faster than getting a timestamp from the operating system. So your best bet is probably to measure it indirectly: take a long-running loop, add a single property access

[v8-users] Seeking help with v8::Platform implementation

V8 experts, I'm having trouble understanding the task scheduling requirements of the embedder's v8::Platform implementation. Some questions: 1. Is it a requirement that all foreground tasks for a given isolate be run on the same thread? 2. Must foreground tasks be run with the isolate lock

Re: [v8-users] Seeking help with v8::Platform implementation

On Fri, Sep 18, 2015 at 4:01 PM, Bit Cortex wrote: > V8 experts, > > I'm having trouble understanding the task scheduling requirements of the > embedder's v8::Platform implementation. Some questions: > > 1. Is it a requirement that all foreground tasks for a given isolate be