[Webkit-unassigned] [Bug 63531] Turn PreloadScanner implementation to a thread based solution

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 10 00:51:23 PST 2013


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


Filip Pizlo <fpizlo at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fpizlo at apple.com




--- Comment #43 from Filip Pizlo <fpizlo at apple.com>  2013-01-10 00:53:14 PST ---
(In reply to comment #42)
> The benefit doesn't seems to be valuable enough.

It would be great if you could summarize your findings.  It's likely that we will want to explore these sorts of optimizations throughout the system.  Probably a lot of the exploration we will do will dead-end, like yours did, simply because this is a tough problem.

So I'm curious about the following:

- To your best estimate, what was the expected speed-up?  The results you posted are for example 1157.39 (ref) versus 1145.5 (your concurrent version), which seems like a speed-up.

- As far as you know, what were the bottlenecks?

I know it's been a long time since you worked on this, but I think that this is a pretty neat case study of taking some part of the code and attempting to make it concurrent.  It would be cool to understand more precisely which parts of your optimization worked, and which parts didn't.

-- 
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