On 6/10/05 12:32 PM, "Bennett Helm" <[EMAIL PROTECTED]> wrote: > I have a 512MB iMac G4 (1.25GHz); it's surely not my hardware that's > the issue. > > Perhaps it's the configuration. Here's what I've got (compiled with > gcc-3.3): > > ./configure --with-frontend=qt --without-x > --prefix=/Applications/LyX-140.app --enable-maintainer-mode > --with-included-gettext --enable-optimization=-Os > --disable-concept-checks --with-version-suffix > --with-qt-dir=/Users/bennett/lyx/qt-mac-free-3.3.4 --without-aiksaurus > > (which means I'm also using qt-mac-free-3.3.4). Furthermore, I've got: > > LDFLAGS="-framework Carbon -framework OpenGL -framework AGL -framework > QuickTime -lz" > > Anything out of line here? Do you have something different? > > Why do I say things are so slow as to be unusable? When I type into an > empty document, lyx starts off (according to top) using about 20% of > CPU. After I've finished typing 4 lines of text, CPU usage for lyx is > up to about 45%. After 10 lines of text, it's up to 75%. By 15 lines of > text, CPU usage is pegged at 100% overall, and text appears on screen > only after a delay -- a delay which increases the longer the document > is, at least up to a point. With a long document, when I type "The > quick brown fox jumps over the lazy dogs." (which takes me about 7 or 8 > seconds), the delay goes up to 9 seconds *after* I finish typing before > all the text appears. The complexity of the document -- whether with or > without math, footnotes, bibliographical entries, cross-references, > etc. -- seems not to be a factor. > > Bennett >
I've been building with exactly the configuration specified in the README.MacOSX file. I thought at one time I needed --disable-concept-checks, but it turns out I've been mistakenly leaving off the 's' at the end for some time (which I guess means the bogus flag was ignored). I just built clean without it - after rerunning ./configure - to verify. I'm building on Tiger, but before 4/29 I'd been building on 10.3 without seeing major issues. I do see the increase in processor use that you report - both on the Mac and on Windows, increasing as the document grows but only if I hammer away at the keyboard. Normal typing doesn't hit that hard on the processor and even hammering doesn't give me delays. I don't know why we're seeing a difference, but I have the same results on three machines (Powerbook, Mini, G5). I'm exposing my ignorance here, but I remember having to download a gettext library at some point, from somewhere. Can a difference like this (assuming yours is different than mine) have an effect? Thanks Rob
