Issue 97544 - DrawText() methods on UNX are much more expensive when invoked by new DrawingLayer
Summary: DrawText() methods on UNX are much more expensive when invoked by new Drawing...
Alias: None
Product: Draw
Classification: Application
Component: viewing (show other issues)
Version: DEV300m37
Hardware: All Unix, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on: 96669
  Show dependency tree
Reported: 2008-12-23 20:19 UTC by Armin Le Grand
Modified: 2017-05-20 10:47 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Armin Le Grand 2008-12-23 20:19:36 UTC
AW: On unix systems, OutputDevice::DrawTextArray/DrawText uses 40% of the
process capacity. Please take a look if this can be enhanced. This is a
follow-up to #i96669#
Comment 1 2008-12-30 14:07:27 UTC
Since the new drawinglayer is responsible for drawing graphics the time spent in DrawText*() methods is 
much higher than before, e.g. for the bugdoc from issue 96669. Preliminary examination suggests that 
most of the time is spent in fontconfig  (which tries to figure out font substitutions).
Comment 2 2008-12-30 14:09:54 UTC
fixed summary line
Comment 3 2009-02-05 13:00:11 UTC
Since issue 96669 got fixed the urgency here is reduced, especially considering that some very critical areas have to 
be changed. Changing the target milestone.

Should the issue become critical for some scenarios there is an easy workaround: set the environment variable SAL_DISABLE_FC_SUBST to anything but '0'.
Comment 4 2009-08-26 07:12:58 UTC
Comment 5 Marcus 2017-05-20 10:47:44 UTC
Reset assigne to the default "".