[Webkit-unassigned] [Bug 146448] JavaScriptCore performance is very bad on Windows

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=146448

--- Comment #50 from peavo at outlook.com ---
(In reply to comment #47)
> I think it's wrong to focus on re-architecting thread id and stack bounds
> here. 
> 
> You'll notice that re-architecting thread id and stack bounds did not make
> JavaScriptCore competitive with Lua. That's a sure sign that it did not fix
> the root problem.
> 
> The profile shows two things:
> 
> (1) We're taking the JSLock just to answer the "is null?" question;
> 
> (2) Taking the JSLock does a lot of work.
> 
> We can fix (1) by not taking the JSLock just to answer trivial type checking
> questions. (Similarly, we probably should not take the JSLock just to create
> trivial types like null.)
> 
> Then we should profile again to see if JSLock is still expensive relative to
> other operations. We can probably make JSLock do a lot less work if we need
> to.

Thanks, these are good points :) I will check the performance without locking in the trivial cases. Maybe we can include the stack bounds optimization on Windows as well?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150722/7ef374b2/attachment.html>