On Tue, Jan 09, 2001 at 04:17:31PM +0000, Alan Burlison wrote: > Some timings based on my app which does intensive object > allocation/deallocation, both built with Forte C workshop 6.1: > > 'Standard' perl configuration (5.6.0) > ------------------------------------- > config_args='-dsOE -Dprefix=/home1/software/perl/debug > -Dinstallprefix=/home1/software/perl/debug > -Dsiteprefix=/home1/software/perl/debug -Ubincompat5005 -D > use64bitint' > optimize='-O' > > real 0m32.07s > user 0m25.61s > sys 0m6.19s > > Optimised perl configuration (5.6.0) > ------------------------------------ > config_args='-dsOE -Dprefix=/home1/software/perl/debug > -Dinstallprefix=/home1/software/perl/debug > -Dsiteprefix=/home1/software/perl/debug -Ubincompat5005 -D > use64bitint -Uusemymalloc -Ud_sigsetjmp -Doptimize=-xO4 -xdepend' > optimize='-xO4 -xdepend' > > real 0m22.32s > user 0m22.11s > sys 0m0.14s > > That is a 30% performance improvement, without changing a single line of > code. This is the main reason I intend ditching siglongjmp when I > integrate 5.6.1 into Solaris. But that 30% is a mix of the effects of -Ud_sigsetjmp and the effects of optimize='-xO4 -xdepend'. How much does performance boost does each give by itself? Tim.Thread Previous | Thread Next