[Webkit-unassigned] [Bug 65277] Provide flexible (in terms of position relative to space) logical word breaker to improve performance of --webkit-visual-word

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 11 22:29:34 PDT 2011


--- Comment #21 from Xiaomei Ji <xji at chromium.org>  2011-08-11 22:29:34 PST ---
(In reply to comment #18)
> I agree with Alexey's sentiment here.  We should try investigating different approaches to see which optimization pays off the most.  When I did optimization in editing, the improvement I saw were in the order of 1-2% in release and 30-40% in debug.  Anything below 1% seems ineffective at best.

when you say 1-2% and 30-40%, are you talking about relative or absolute numbers?

For example, rightWordPosition from 3.8% to 3.4%, is the improvement 0.4% or ~10% (0.4/3.8)?
collectWordbreakInBox has 30%+ gain (0.7/1.9). And I believe it and rightWordBoundary should improve further if we decrease the collectWordBreakInBox calls in rightWordBoundary.

I think this is the 1st step of improvement (reduce the number of calls to nextBoundary()), after which, the cost of nextBoundary() will be more evident, and that is the next step for improvement.

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