On Sep 21, 2005, at 11:56 AM, Jean-Marc Lasgouttes wrote:

"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:


Bennett> I've just recompiled myself with --disable-stdlib-debug.
Bennett> Things in general (on Mac) seem to be faster *except* typing
Bennett> speed in long documents, which is not noticeably improved. I
Bennett> get the lag Angus describes even with typing normally (and
Bennett> I'm not a terrifically fast typist). I would say it's still
Bennett> unusable on Mac for anything but very short documents -- less
Bennett> than 2 pages.

If only we were able to get good profiles showing the problem...

I've tried! -- Perhaps I should use something other than Shark.app. Suggestions?

What are the exact conditions where this happens? Does typing at the
end of a paragraph make things better? Is it really related to the
size of the document, or to the amount of text on screen?

I cannot -- even with gibberish -- type faster than LyX can handle when the document is otherwise empty, and LyX doesn't use many processor resources in this case.

After 5-10 lines of text are entered, it becomes noticeable that LyX is consuming more processor time than it had, though it's still fast enough that I don't detect a lag.

With more than 20 lines of text, it's possible for me to type fast enough that the CPU is pegged at 100% and I begin to notice a lag, though I would characterize it as usable.

With more than 25 lines, the lag is quite annoying: it takes a second or so to catch up after typing in a sentence.

In every case, I'm simply typing ordinary text: no math insets, no footnotes, no graphics, no nothing. Adding these things doesn't seem to make a difference: the issue really has to do with normal text, as far as I can see.

The issue seems to be the amount of text on the screen rather than the size of the document: if I scroll down to the bottom of a large document so that only a single line is visible on screen, I can type at a normal speed. Moreover, the situation improves when I make the LyX window very small and type, even when the window is filled with text; conversely, larger windows seem to slow things down more.

When the screen is filled with text, there is only a slight improvement in speed in typing at the end of a paragraph rather than the middle. Typing in a new paragraph is the same as typing at the end of an old paragraph.

Bennett

Reply via email to