Re: [v8-users] Strange Scavenge allocation failure cause dramatical performance dropdown

On Wed, Dec 6, 2017 at 3:55 AM, Huabin Ling wrote: > Thanks for the informations Michael > > I attached a saved trace record here, and I notice that in each frame there > is a relatively long "CommandBufferProxyImpl::WaitForToken", which doesn't > happen when the

[v8-users] Re: Changes to the V8 API changes doc

Yeah I long gave up on getting any actual sort of documentation for the project, so why bother keeping any. On Tuesday, December 5, 2017 at 1:10:25 AM UTC-8, Michael Hablich wrote: > > Hi folks, > > *you can stop reading now if you don't know what the 'V8 API changes >

Re: [v8-users] Strange Scavenge allocation failure cause dramatical performance dropdown

At first sight, the Scavenge pause times seem unrelated to your problem. Can you take a trace using Chrome's tracing infrastructure? See [1]. This one will help dig down into what is causing the slowdown. Rest inlined. [1]

[v8-users] Re: Strange Scavenge allocation failure cause dramatical performance dropdown

By the way, the allocation failure log doesn't occur before the performance drop down. If a switch page and wait a moment, then return to the test case page, there is chance that chrome stops printing "allocation failure" log and the frame time returns to normal, but it will drop down again in

[v8-users] Strange Scavenge allocation failure cause dramatical performance dropdown

Hi, I'm recently developing a rendering engine for WebGL, but met a serious performance issue caused by Scavenge allocation failure issue. I have a test case which add more and more sprites on the screen, when it's arriving at about 7000 (and stop adding more), the cost of engine is about

[v8-users] Changes to the V8 API changes doc

Hi folks, *you can stop reading now if you don't know what the 'V8 API changes ' doc is :-).* We are no longer planning on adding a list of changes to the V8 API in the 'V8 API changes