Try running a DOM benchmark while there is a content script that's waiting for a message from a background page.
Adam On Thu, Nov 5, 2009 at 12:12 PM, Anton Muhin <[email protected]> wrote: > Adam, all, > > I've got http://codereview.chromium.org/355047/ which should speed up > accessing isolated worlds (it at least passes layout tests). > > Could someone either see if it helps or give me instructions how to bench it? > > yours, > anton. > > On Tue, Oct 27, 2009 at 8:04 PM, Anton Muhin <[email protected]> wrote: >> On Tue, Oct 27, 2009 at 8:00 PM, Adam Barth <[email protected]> wrote: >>> On Tue, Oct 27, 2009 at 9:52 AM, Anton Muhin <[email protected]> wrote: >>>> if we're sure accessing hidden property is a bottleneck, it should be >>>> easily solvable: for long time I was toying idea to compile this code >>>> into native, but didn't see compelling enough reason to do that. The >>>> easy way to measure it would be to hack stuff a bit and put data as in >>>> internal field or just add another getter to context. If you like, I >>>> can try to do something like that, but I need a simplistic benchmark >>>> to estimate performance gain. >>> >>> I suspect you'll see a performance gain on any simple DOM benchmark >>> that runs in the isolated world. That code path is hit on every >>> wrapper lookup. >> >> Ok, I will try to have a look at it this week. >> >> yours, >> anton. >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
