Helge Hafting wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a long time, and then
Helge Hafting wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a "long" time, and
On Fri, Sep 28, 2007 at 09:52:29AM +0200, Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
Martin Vermeer wrote:
On Fri, Sep 28, 2007 at 09:52:29AM +0200, Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to
On Fri, Sep 28, 2007 at 09:52:29AM +0200, Abdelrazak Younes wrote:
> Abdelrazak Younes wrote:
> > Helge Hafting wrote:
> >>
> >> Arrange one paragraph with 25 lines.
> >> Type a string og W's in the next paragraph. The W's comes out with
> >> great speed until this second paragraph needs to
Martin Vermeer wrote:
On Fri, Sep 28, 2007 at 09:52:29AM +0200, Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a long time, and then things continue at great speed. The
linewrap
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a long time, and then things continue at great speed. The
linewrap
Depends on what you mean. it's also bad
yeah, that's what i meant
Ideally we'd like to redraw on the inset button and nothing
else. We may achieve this goal before 1.6 with a bit more of cleanup.
ok
Leuven, E. wrote:
when i hover a collapsable i see
{111}[110]
is this good or bad?
Depends on what you mean. It is good because it is what's expected (the
whole screen is redrawn on mouse hover) but it's also bad because of
that. Ideally we'd like to redraw on the inset button and nothing
Helge Hafting wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a long time, and then things continue at great
Abdelrazak Younes wrote:
Exactly :-)
More seriously, I've cleaned up the design quite a quite now and I
think some of these optimizations should be possible now. You are
welcome to give me a hand ;-)
Optimizing drawing would surely be interesting - if I can find
enough contigous free time.
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a long time, and then things continue at great speed. The
linewrap
when i hover a collapsable i see
{111}[110]
is this good or bad?
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a "long" time, and then things continue at great speed. The
linewrap
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a "long" time, and then things continue at great speed. The
linewrap
> Depends on what you mean. it's also bad
yeah, that's what i meant
> Ideally we'd like to redraw on the inset button and nothing
> else. We may achieve this goal before 1.6 with a bit more of cleanup.
ok
Leuven, E. wrote:
when i hover a collapsable i see
{111}[110]
is this good or bad?
Depends on what you mean. It is good because it is what's expected (the
whole screen is redrawn on mouse hover) but it's also bad because of
that. Ideally we'd like to redraw on the inset button and nothing
Helge Hafting wrote:
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a "long" time, and then things continue at great
Abdelrazak Younes wrote:
Exactly :-)
More seriously, I've cleaned up the design quite a quite now and I
think some of these optimizations should be possible now. You are
welcome to give me a hand ;-)
Optimizing drawing would surely be interesting - if I can find
enough contigous free time.
Abdelrazak Younes wrote:
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a "long" time, and then things continue at great speed. The
linewrap
when i hover a collapsable i see
{111}[110]
is this good or bad?
Martin Vermeer wrote:
Would it be an idea to first try LyX's own -dbg painting, to see how
repainting is being done? Especially in problem cases LyX may be simply
doing too much.
lyx -dbg painting produces no extra output,
other than telling me that it sets the debug level to 'painting'
Helge Hafting wrote:
Now this is interesting. If the number of {}'s is an indication, the LyX
does
18 times as much work when typing in a partially visible paragraph. And
yes,
with this window size, there were exactly 18 lines in the paragraph.
I hope this gives an indication of what's
Helge Hafting wrote:
Now this is interesting. If the number of {}'s is an indication, the
LyX does 18 times as much work when typing in a partially visible
paragraph. And yes, with this window size, there were exactly 18
lines in the paragraph.
Please try again with rev 20536.
Abdel.
Abdelrazak Younes wrote:
Helge Hafting wrote:
Now this is interesting. If the number of {}'s is an indication, the
LyX does 18 times as much work when typing in a partially visible
paragraph. And yes, with this window size, there were exactly 18
lines in the paragraph.
Please try again with
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a long time, and then things continue at great speed. The
linewrap
is noticeable, and lyx -dbg
Martin Vermeer wrote:
Would it be an idea to first try LyX's own -dbg painting, to see how
repainting is being done? Especially in problem cases LyX may be simply
doing too much.
"lyx -dbg painting" produces no extra output,
other than telling me that it sets the debug level to 'painting'
Helge Hafting wrote:
Now this is interesting. If the number of {}'s is an indication, the LyX
does
18 times as much work when typing in a partially visible paragraph. And
yes,
with this window size, there were exactly 18 lines in the paragraph.
I hope this gives an indication of what's
Helge Hafting wrote:
Now this is interesting. If the number of {}'s is an indication, the
LyX does 18 times as much work when typing in a partially visible
paragraph. And yes, with this window size, there were exactly 18
lines in the paragraph.
Please try again with rev 20536.
Abdel.
Abdelrazak Younes wrote:
Helge Hafting wrote:
Now this is interesting. If the number of {}'s is an indication, the
LyX does 18 times as much work when typing in a partially visible
paragraph. And yes, with this window size, there were exactly 18
lines in the paragraph.
Please try again with
Helge Hafting wrote:
Arrange one paragraph with 25 lines.
Type a string og W's in the next paragraph. The W's comes out with
great speed until this second paragraph needs to linewrap. The wrap
takes a "long" time, and then things continue at great speed. The
linewrap
is noticeable, and lyx
Richard Heck wrote:
Can people on Linux (at least) try this: Open a new file; open a LyX
note; type. I get amazing slowness. A little experimenting suggests
that this behavior shows itself whenever I am typing at the end of a
text inset. For example, if I go to the end of the file, then I
Helge Hafting wrote:
Richard Heck wrote:
Can people on Linux (at least) try this: Open a new file; open a LyX
note; type. I get amazing slowness. A little experimenting suggests
that this behavior shows itself whenever I am typing at the end of a
text inset. For example, if I go to the end
Abdelrazak Younes wrote:
Helge Hafting wrote:
Richard Heck wrote:
Can people on Linux (at least) try this: Open a new file; open a LyX
note; type. I get amazing slowness. A little experimenting suggests
that this behavior shows itself whenever I am typing at the end of a
text inset. For
I'd like to try, but how do I do that?
what OS are you running ?
pavel
Pavel Sanda wrote:
I'd like to try, but how do I do that?
what OS are you running ?
pavel
linux
Helge Hafting ha scritto:
what OS are you running ?
pavel
Probably, it is more interesting to know what CPU and/or graphic
adapter.
I can't see so much slowness on my Ubuntu Fesity. Running on a
laptop with a NVIDIA GeForce Go 6200 card and this CPU:
processor : 0
vendor_id :
linux
use gprof then.
you need to compile lyx with enabled profiling.
try configure --enable-profile --disable-stdlib-debug and make sure
that when making gcc gets -pg option (which is not case for me eg,
dunno why).
then try
gprof /usr/bin/lyx gmon.out gprof.out
pavel
Pavel Sanda [EMAIL PROTECTED] writes:
linux
use gprof then.
you need to compile lyx with enabled profiling.
try configure --enable-profile --disable-stdlib-debug and make sure
that when making gcc gets -pg option (which is not case for me eg,
dunno why).
then try
gprof /usr/bin/lyx
gprof won't say anything about the time spent in qt, X11 and libc. It
is pretty useless for UI-related profiles.
i dont understand this. gprof doesnt tell you e.g. that we are spending 90%
time in whole-screen-repainting funtion in our code ?
pavel
Pavel Sanda [EMAIL PROTECTED] writes:
gprof won't say anything about the time spent in qt, X11 and libc. It
is pretty useless for UI-related profiles.
i dont understand this. gprof doesnt tell you e.g. that we are spending 90%
time in whole-screen-repainting funtion in our code ?
It does
On Wed, Sep 26, 2007 at 06:04:14PM +0200, Jean-Marc Lasgouttes wrote:
Pavel Sanda [EMAIL PROTECTED] writes:
gprof won't say anything about the time spent in qt, X11 and libc. It
is pretty useless for UI-related profiles.
i dont understand this. gprof doesnt tell you e.g. that we are
Martin Vermeer [EMAIL PROTECTED] writes:
Would it be an idea to first try LyX's own -dbg painting, to see how
repainting is being done? Especially in problem cases LyX may be simply
doing too much.
Yes.
JMarc
Richard Heck wrote:
Can people on Linux (at least) try this: Open a new file; open a LyX
note; type. I get amazing slowness. A little experimenting suggests
that this behavior shows itself whenever I am typing at the end of a
text inset. For example, if I go to the end of the file, then I
Helge Hafting wrote:
Richard Heck wrote:
Can people on Linux (at least) try this: Open a new file; open a LyX
note; type. I get amazing slowness. A little experimenting suggests
that this behavior shows itself whenever I am typing at the end of a
text inset. For example, if I go to the end
Abdelrazak Younes wrote:
Helge Hafting wrote:
Richard Heck wrote:
Can people on Linux (at least) try this: Open a new file; open a LyX
note; type. I get amazing slowness. A little experimenting suggests
that this behavior shows itself whenever I am typing at the end of a
text inset. For
> I'd like to try, but how do I do that?
what OS are you running ?
pavel
Pavel Sanda wrote:
I'd like to try, but how do I do that?
what OS are you running ?
pavel
linux
Helge Hafting ha scritto:
what OS are you running ?
pavel
Probably, it is more interesting to know what CPU and/or graphic
adapter.
I can't see so much slowness on my Ubuntu Fesity. Running on a
laptop with a NVIDIA GeForce Go 6200 card and this CPU:
processor : 0
vendor_id :
> linux
use gprof then.
you need to compile lyx with enabled profiling.
try configure --enable-profile --disable-stdlib-debug and make sure
that when making gcc gets -pg option (which is not case for me eg,
dunno why).
then try
gprof /usr/bin/lyx gmon.out > gprof.out
pavel
Pavel Sanda <[EMAIL PROTECTED]> writes:
>> linux
>
> use gprof then.
> you need to compile lyx with enabled profiling.
> try configure --enable-profile --disable-stdlib-debug and make sure
> that when making gcc gets -pg option (which is not case for me eg,
> dunno why).
>
> then try
> gprof
> gprof won't say anything about the time spent in qt, X11 and libc. It
> is pretty useless for UI-related profiles.
i dont understand this. gprof doesnt tell you e.g. that we are spending 90%
time in whole-screen-repainting funtion in our code ?
pavel
Pavel Sanda <[EMAIL PROTECTED]> writes:
>> gprof won't say anything about the time spent in qt, X11 and libc. It
>> is pretty useless for UI-related profiles.
>
> i dont understand this. gprof doesnt tell you e.g. that we are spending 90%
> time in whole-screen-repainting funtion in our code ?
On Wed, Sep 26, 2007 at 06:04:14PM +0200, Jean-Marc Lasgouttes wrote:
> Pavel Sanda <[EMAIL PROTECTED]> writes:
>
> >> gprof won't say anything about the time spent in qt, X11 and libc. It
> >> is pretty useless for UI-related profiles.
> >
> > i dont understand this. gprof doesnt tell you e.g.
Martin Vermeer <[EMAIL PROTECTED]> writes:
> Would it be an idea to first try LyX's own -dbg painting, to see how
> repainting is being done? Especially in problem cases LyX may be simply
> doing too much.
Yes.
JMarc
56 matches
Mail list logo
