This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Performance report (350MHz i686 configured asi386-unknown-freebsd4.8)
- From: "B. Kosnik" <bkoz at nabi dot net>
- To: rittle at labs dot mot dot com
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Tue, 24 Jun 2003 13:06:04 -0500
- Subject: Re: Performance report (350MHz i686 configured asi386-unknown-freebsd4.8)
- References: <200306240849.h5O8nCWQ036833@latour.rsch.comm.mot.com>
>Run without -pthread:
>
>allocator.cc default 1241r 1234u 0s 0pf
>allocator.cc malloc 2433r 2163u 2s 0pf
>allocator.cc mt 1389r 1303u 0s 0pf
>Run with -pthread (by manually hacking libstdc++-v3/scripts/check_performance):
>
>allocator.cc default 1190r 1141u 0s 0pf
>allocator.cc malloc 426r 399u 1s 0pf
>allocator.cc mt 480r 468u 0s 0pf
About what I am seeing on linux.
I don't know how to proceed on sorting out the default allocator issue.
I like the suggestion here about switching over to mt_alloc if pthreads:
http://gcc.gnu.org/ml/libstdc++/2003-06/msg00119.html
That seems easiest to do, considering the alternatives.
>(BTW, yes, I think we should run the test cases with and without
>e.g. -pthread esp. if we find it matters even for non-threaded cases.
>I'll make it possible to run either way without having to change a
>srcdir file perhaps by respecting the same RUNTESTFLAG format that
>dejagnu honors.)
Sounds like a good idea.
-benjamin