From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5511 invoked by alias); 23 Jan 2004 02:34:12 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 5491 invoked by uid 48); 23 Jan 2004 02:34:11 -0000 Date: Fri, 23 Jan 2004 02:34:00 -0000 Message-ID: <20040123023411.5490.qmail@sources.redhat.com> From: "pinskia at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040123001452.13823.devison@pacificit.co.nz> References: <20040123001452.13823.devison@pacificit.co.nz> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/13823] Significant performance issue with std::map on multiple threads on dual processor - possibly default allocator X-Bugzilla-Reason: CC X-SW-Source: 2004-01/txt/msg02870.txt.bz2 List-Id: ------- 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