This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/46659] std::list iterator debugging (_GLIBCXX_DEBUG) is much slower than stlport's one.


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46659

--- Comment #3 from Pawel Sikora <pluto at agmk dot net> 2010-11-25 18:40:28 UTC ---
(In reply to comment #2)
> Let's add Francois in CC, he knows STLPort pretty well. And somebody should
> profile this difference, redo the tests for current mainline (which already has
> some performance improvement from Francois), etc.

with the current mainline i have following results
on my personal Q9300 cpu:

50000 elements:

$ time ./t-libstdcxx
./t-libstdcxx  11,17s user 0,00s system 99% cpu 11,171 total
$ time ./t-stlport
./t-stlport  7,18s user 0,00s system 99% cpu 7,180 total

100000 elements:

$ time ./t-libstdcxx
./t-libstdcxx  68,26s user 0,00s system 99% cpu 1:08,28 total
$ time ./t-stlport
./t-stlport  31,84s user 0,00s system 99% cpu 31,853 total

200000 elements:

$ time ./t-libstdcxx
./t-libstdcxx  316,08s user 0,02s system 99% cpu 5:16,13 total
$ time ./t-stlport
./t-stlport  184,10s user 0,01s system 99% cpu 3:04,12 total


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]