On Fri, May 19, 2006 at 11:50:50PM +0200, Abdelrazak Younes wrote:
> It seems that font_metrics::width is called two times within
> LyXText::redoParagraph, once in LyXText::rowBreakPoint and another in
> ::RowPainter::paintChars; I think this could be optimized out, Martin?
It's not easy. We tri
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> I'm not convinced. How? And isn't this (font metrics) being
Martin> cached in Qt?
It is supposed to, indeed. We still have some caching code for older
qt3 versions. You may want to reactivate it and see what happens.
JMarc
Abdelrazak Younes a écrit :
Martin Vermeer a écrit :
It doesn't look to me that this is caching anything. Is it?
Right, now I look at it, it should be something like this:
if (!fi)
fi = new QLFontInfo(f);
fontinfo_[f.family()][f.series()][f.realShape()][f.size()] = fi;
return *fi;
Martin Vermeer a écrit :
On Sat, May 20, 2006 at 03:32:05PM +0200, Abdelrazak Younes wrote:
Abdelrazak Younes a écrit :
Martin Vermeer a écrit :
...
Hum, this code in "qfont_loader.C" looks suspicious:
__
QLFontInfo & fontinfo(LyXFont const &
On Sat, May 20, 2006 at 03:32:05PM +0200, Abdelrazak Younes wrote:
> Abdelrazak Younes a écrit :
> >Martin Vermeer a écrit :
...
> Hum, this code in "qfont_loader.C" looks suspicious:
> __
>
> QLFontInfo & fontinfo(LyXFont const & f) {
> QLFontInfo * & fi
On Sat, May 20, 2006 at 01:46:42PM +0200, Abdelrazak Younes wrote:
> Martin Vermeer a écrit :
...
> >>It seems that font_metrics::width is called two times within
> >>LyXText::redoParagraph, once in LyXText::rowBreakPoint and another in
> >>::RowPainter::paintChars; I think this could be optimi
Abdelrazak Younes a écrit :
Martin Vermeer a écrit :
On Fri, May 19, 2006 at 11:50:50PM +0200, Abdelrazak Younes wrote:
| | | | + 510.6 ms LyXText::rowBreakPoint(int, Row&) const (lyx)
| | | | | + 457.7 ms font_metrics::width(char, LyXFont const&) (lyx)
| | | | + 2417.1 ms ::RowPainter::paint
Martin Vermeer a écrit :
On Fri, May 19, 2006 at 11:50:50PM +0200, Abdelrazak Younes wrote:
| | | | + 510.6 ms LyXText::rowBreakPoint(int, Row&) const (lyx)
| | | | | + 457.7 ms font_metrics::width(char, LyXFont const&) (lyx)
| | | | + 2417.1 ms ::RowPainter::paintFromPos(int&) (lyx)
| | | |
On Fri, May 19, 2006 at 11:50:50PM +0200, Abdelrazak Younes wrote:
> Bennett Helm a écrit :
> >generate a report with those data.) Nonetheless, what's obvious from
> >that is the amount of time spent in QPainter (see, e.g., near the top
> >and near the bottom; for the latter, the 1710.0 ms is for
Bennett Helm <[EMAIL PROTECTED]> writes:
| On May 19, 2006, at 11:34 AM, Abdelrazak Younes wrote:
|
| > No, I think it would be better if you pass
| > --disable-debug --disable-stdlib-debug
| > instead of:
| > --enable-debug --enable-stdlib-debug
|
| Without --enable-debug, at least, I c
Bennett Helm a écrit :
generate a report with those data.) Nonetheless, what's obvious from
that is the amount of time spent in QPainter (see, e.g., near the top
and near the bottom; for the latter, the 1710.0 ms is for the whole
tree, but of that QPainter takes up 1695.7 ms), font_metrics::wid
On May 19, 2006, at 2:36 PM, Abdelrazak Younes wrote:
Bennett Helm a écrit :
On May 19, 2006, at 12:13 PM, Abdelrazak Younes wrote:
I can do that too. There are 2 options for sorting the report --
via a column labeled "Self" and one labeled "Total". This (as my
others have been) is sorted b
Bennett Helm a écrit :
On May 19, 2006, at 12:13 PM, Abdelrazak Younes wrote:
I can do that too. There are 2 options for sorting the report -- via a
column labeled "Self" and one labeled "Total". This (as my others have
been) is sorted by "Total", again arbitrarily cut near the top. Let me
kn
On May 19, 2006, at 12:13 PM, Abdelrazak Younes wrote:
Bennett Helm a écrit :
On May 19, 2006, at 11:34 AM, Abdelrazak Younes wrote:
No, I think it would be better if you pass
--disable-debug --disable-stdlib-debug
instead of:
--enable-debug --enable-stdlib-debug
Without --enable-debug
Bennett Helm a écrit :
On May 19, 2006, at 11:34 AM, Abdelrazak Younes wrote:
No, I think it would be better if you pass
--disable-debug --disable-stdlib-debug
instead of:
--enable-debug --enable-stdlib-debug
Without --enable-debug, at least, I can't get function names in the
profile
On May 19, 2006, at 11:34 AM, Abdelrazak Younes wrote:
No, I think it would be better if you pass
--disable-debug --disable-stdlib-debug
instead of:
--enable-debug --enable-stdlib-debug
Without --enable-debug, at least, I can't get function names in the
profile.
You use cas
Bennett Helm a écrit :
Well, here is the beginning of the profile report -- arbitrarily cut off
near the top. As I have done with previous profiles, this is produced
with: tree view; system libraries charged to callers; 30-second sample,
with me typing constantly during the sampling.
LyX was
17 matches
Mail list logo
