Lars Gullik Bjønnes wrote:
Helge Hafting <[EMAIL PROTECTED]> writes:
| On Wed, Dec 07, 2005 at 04:58:51PM +0100, Jean-Marc Lasgouttes wrote:
| > >>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| >
| > Lars> I also tried to do some profiling on this, but failed to get
| > Lars> anything to pinpoint. Also on my box startup times are not bad
| > Lars> at all... (sub-second)
| >
| > I clearly see a difference between 1.3.x and 1.4.x, but the times are
| > reasonably short.
|
| Evereybody except me get sub-second startup times?
| That is good, lyx is probably ok with me making a mistake then.
| It'd sure be interesting if anyone have an idea what I do wrong.
|
| My configure command, using optimizations and disabling
| some costly debugging. Are there perhaps other things that impact speed?
|
|
| $ ./configure --prefix=/usr/local --with-frontend=qt --with-gnu-ld
| --with-qt-includes=/usr/include/qt3 --disable-stdlib-debug
| --disable-concept-checks --enable-assertions CFLAGS=-O2 CPPFLAGS=-O2
Even on a build with this:
./configure --with-frontend=qt --disable-debug
And when starting I get sub-2-second startup. (cached, no disk read needed)
This in on a AMD XP 2400
The only thing I see with your configure line that could be changed in
the last two variables that you set... (btw. does it work to set them
last on the command line?)
To set optimization level you should use --enable-optimization='-O2'
Ok, tried this. More exactly:
$ ./configure --prefix=/usr/local --with-frontend=qt --with-gnu-ld
--with-qt-includes=/usr/include/qt3 --disable-debug
--disable-concept-checks --enable-optimization=-O2
Lyx takes 5 seconds to start on a pentium M, 2.4 GHz. The 3 seconds
previously mentioned was on the 1.8GHz opteron. I have
compiled with these options there too, and will time it again
when I get to the machine. (No use timing lyx over the ADSL line, we'll be
waiting for tunneled X in that case.)
I am now trying -Os instead of -O2. If that doesn't help, I'll try your
config to check if there is something weird going on, like
--with-gnu-ld or one of the others unexpectedly triggering something.
Hmm are these 64bit binaries or 32bit? (does that matter?)
I hope not! This was from the opteron, so all libraries was 64-bit.
It is the fastest of my two test machines anyway.
On my FC4 running on an AMD64 XP3500 all the above libraries point
into some lib64 dir. (might very well be one of the differenced
between debian and fedora)
Yes. Debians amd64 is a 64-bit port, so the 64-bit libraries is in
/lib. There
are no 32-bit stuff at all, unless you install it in order to support
the odd
32-bit binary-only program, like adobe acrobat or wine. (Well, wine is
open source but it runs 32-bit proprietary sw...)
Debian has a /lib64, but it is merely a link to /lib.
Helge Hafting
