On Fri, Dec 09, 2005 at 04:07:50PM -0500, Bennett Helm wrote: > On Dec 9, 2005, at 3:03 PM, Martin Vermeer wrote: > > >On Thu, Dec 08, 2005 at 12:31:40PM -0500, Bennett Helm wrote: > >>On Dec 8, 2005, at 11:09 AM, Jean-Marc Lasgouttes wrote: > >> > >>>>>>>>"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes: > > > > > >>It's a little hard to tell the order of events given that things > >>happen so quickly. But it seems like as you type, the individual > >>character that gets typed gets updated, then the info bar at the > >>bottom of the window is updated, and then the whole text area of the > >>window is updated. It's that last item that seems significant: the > >>entire window is updated with each keystroke. > > > >Bennett, > > > >the attached should produce a noticable speedup. > > > >(Lars likes simple patches :) > > Well, I'm comparing apples and oranges a bit, but I'm not noticing > much of a speed-up. > > I've applied your patch to the version of lyx I compile with gcc-4.0 > (because the gcc-3.3 version I'm currently using for profiling). > Comparing that against a stable gcc-3.3-compiled version (without > profiling info and otherwise configured identically), I don't notice > any difference just by typing. > > Being a bit more systematic: When I type a sentence into a long > paragraph -- the same conditions under which it took me 8 seconds to > type and lyx (gcc-3.3) 16-17 seconds to display -- it takes 15 > seconds to display with the patched version. I've done it several > times with reasonably reliable results, so I think it is fair to say > there is a minor speed-up. > > Using Quartz Debug to look at window refreshes, I don't notice any > difference. > > Finally, I applied the patch to the version of lyx compiled with > gcc-3.3 with profiling info, ran Shark (in the same way I did > before), and placed the report here: <http://edisk.fandm.edu/ > bennett.helm/LyX/shark-profile-2.txt.zip>. > > Bennett
Quote: "Done. I opened lyx, opened a file with a long paragraph in an >Bennett> inset, typed a sentence in the middle of that paragraph (and >Bennett> waited until the screen caught up), and then quit." Is this what you did in all these tests? Just one big paragraph inside an inset? If so, I understand why you see no big difference. If not, 1) can you use one inset per paragraph? Does it help? 2) is the long paragraph equally slow to type into without the inset around it? - Martin
pgpITXb1R8uTb.pgp
Description: PGP signature
