One, check your malloc option settings. FreeBSD-current defaults to the AJ setting to flush out errors but this has a significant performance hit.
See the malloc(3) manpage for details. You don't say which version you were running before so this is the most specific advice I can give you. Poul-Henning In message <000001c1a16a$ec95cc50$022a17ac@simplex>, "Duraid Madina" writes: >Hi all, > > I have a CPU-bound (well, 'malloc-bound' ;) program which takes >about 20 seconds to run on a 'fast' PC (Pentium3-1000, Athlon XP1600 >etc) - the source is available as >http://www.idesign.fl.net.au/malloc_pain/malloc_pain.tar.gz (NOTE: you >*will* need GCC 3 (or more recent) to compile it). At any rate, I did >the cvsup/buildkernel/buildworld thing this morning (I'm running >5-CURRENT on an SMP box), and now that same program takes about half an >hour to run, rather than 20 seconds. Curiously, it reports about 20% >system time (whereas previously there was negligible system time) > > Any idea what might be going on? > > Duraid > >P.S. to run it: > >gcc -c mt19937b-int.c >g++ Graph.cpp mt19937b-int.o >./a.out > >Known to compile okay with GCC 3.0.3 and 3.1 > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-hackers" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
