[Bug libstdc++/13823] Significant performance issue with std::map on multiple threads on dual processor - possibly default allocator

["devison at pacificit dot co dot nz" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From devison at pacificit dot co dot nz  2004-01-23 02:41 -------
Subject: Re:  Significant performance issue with std::map
 on multiple threads on dual processor - possibly default allocator


Thanks for the fast response!
Is there a per thread pool_alloc currrently available that is recommended
for use?
There looks like evidence of one, in the file
include/c++/3.3.2/bits/stl_pthread_alloc.h

(should I post questions like this via bugzilla?)


----- Original Message -----
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: <devison@pacificit.co.nz>
Sent: Friday, January 23, 2004 3:34 PM
Subject: [Bug libstdc++/13823] Significant performance issue with std::map
on multiple threads on dual processor - possibly default allocator


>
> ------- Additional Comments From pinskia at gcc dot gnu dot org
2004-01-23 02:34 -------
> Confirmed on the mainline but it is not as bad as 3.3 was.  The problem is
that is the a mutex is
> getting locked too much, I do not know if this is ever going to be fixed
except by per thread
> pool_alloc.
>
> --
>            What    |Removed                     |Added
> --------------------------------------------------------------------------
--
>            Severity|normal                      |enhancement
>              Status|UNCONFIRMED                 |NEW
>           Component|c++                         |libstdc++
>      Ever Confirmed|                            |1
>    Last reconfirmed|0000-00-00 00:00:00         |2004-01-23 02:34:08
>                date|                            |
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13823
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
>




-- 


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