[STDCXX-227] std::basic_string shared static data a performance bottleneck in SMP situations

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 4.1.2, 4.1.3
• Component/s: 21. Strings

Environment

all

• Assignee: Unassigned
• Reporter: Martin Sebor
• Created: 29/Jun/06 01:31
• Updated: 01/Jun/07 21:08

Description

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.