To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=106127
User hdu changed the following:
What |Old value |New value
================================================================================
Summary|Some minor speedups for ba|Some speedups for basegfx
|segfx |
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Thu Oct 22 10:03:12 +0000
2009 -------
Done in CWS vcl106: with all the optimizations above the basegfx::solver still
consumes 90% of the time in
the i105769-testcase. Especially the current implementations of bezier-bezier
and bezier-line solvers are
expensive. They already were avoided in the many cases where there is no
overlap at all between both
candidates, but it they were still called too often. Even when the
control-bounds just touched the calls
were done. This is a good idea for non-neighboring edges but neighboring edges
always touch because
they have one edge-point in common -> solved by introducing
Range::overlapsMore() and using it for
neighboring edges. This reduces the cost of addPointsAtCutsAndTouches() by a
factor of 2.3. There is still
more potential as the neighboring edges first-segment and last-segments are
still fully tested.
Ideas for a better name for Range::overlapsMore() are welcome
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
