incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <j...@apache.org>
Subject [jira] Created: (STDCXX-227) std::basic_string shared static data a performance bottleneck in SMP situations
Date Wed, 28 Jun 2006 18:32:29 GMT
std::basic_string shared static data a performance bottleneck in SMP situations
-------------------------------------------------------------------------------

         Key: STDCXX-227
         URL: http://issues.apache.org/jira/browse/STDCXX-227
     Project: C++ Standard Library
        Type: Improvement

  Components: 21. Strings  
    Versions: 4.1.2, 4.1.3    
 Environment: all
    Reporter: Martin Sebor


Moved from the Rogue Wave bug tracking database:

****Created By: yoder @ Oct 22, 2001 03:26:34 PM****

Customer maintains that shared static data such as the null object in basic_string is a performance
bottleneck in SMP situations. The offered solution is to make it a thread specific object.

****Modified By: sebor @ Nov 14, 2001 06:28:14 PM****
Only reads from or writes to RAM (as opposed to ROM) may potentially incur a performance penalty.
Reading the address of a shared object (which is what string does in most cases) is fast.
To help the OS prevent any performance penalty at all, the empty string literal (or the entire
null reference object) should be put in ROM (by making sure it is a POD, which it is, and
by declaring it const, which it currently isn't).

****Modified By: sebor @ Oct 02, 2002 10:26:11 AM****
p4 describe 109937 makes the null reference type a POD. It's still not const, though.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message