public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/13823] Significant performance issue with std::map on multiple threads on dual processor - possibly default allocator
Date: Fri, 23 Jan 2004 02:34:00 -0000	[thread overview]
Message-ID: <20040123023411.5490.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040123001452.13823.devison@pacificit.co.nz>


------- 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


  parent reply	other threads:[~2004-01-23  2:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  0:15 [Bug c++/13823] New: " devison at pacificit dot co dot nz
2004-01-23  0:18 ` [Bug c++/13823] " devison at pacificit dot co dot nz
2004-01-23  0:49 ` richard at redspider dot co dot nz
2004-01-23  2:34 ` pinskia at gcc dot gnu dot org [this message]
2004-01-23  2:41 ` [Bug libstdc++/13823] " devison at pacificit dot co dot nz
2004-01-23  2:44 ` pinskia at gcc dot gnu dot org
2004-01-23  3:26 ` rittle at latour dot rsch dot comm dot mot dot com
2004-01-23  3:38 ` ljrittle at gcc dot gnu dot org
2004-01-23  3:58 ` devison at pacificit dot co dot nz
2004-01-23  3:58 ` ljrittle at gcc dot gnu dot org
2004-01-23  4:14 ` rittle at latour dot rsch dot comm dot mot dot com
2004-01-23  5:31 ` devison at pacificit dot co dot nz
2004-01-23  6:01 ` rittle at latour dot rsch dot comm dot mot dot com
2004-01-23 12:48 ` devison at pacificit dot co dot nz
2004-01-23 20:47 ` rittle at latour dot rsch dot comm dot mot dot com
     [not found] <bug-13823-4@http.gcc.gnu.org/bugzilla/>
2024-06-13 14:30 ` redi at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040123023411.5490.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).