[Webkit-unassigned] [Bug 118573] Optimize the thread locks for API Shims

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 12 15:55:01 PDT 2013


--- Comment #9 from Yi Shen <max.hong.shen at gmail.com>  2013-07-12 15:57:04 PST ---
I do have a more real-world test for this. Will add a patch for review and post a real-world benchmark next week. Thanks in advanced!
(In reply to comment #8)
> > Thanks for review. How about removing the API thread lock/unlock for the VM which has an exclusive thread? For example, WK2 is using JSC APIs within the injected bundle, which runs in the WebCore's exclusive VM. I believe it is thread safety when executing JSC APIs in the WebCore's VM.  
> I think a specialized design like that would need a more real-world benchmark to justify itself.
> There are lots of opportunities for optimizing JSLock.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list