You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jeremy Leung (JIRA)" <ji...@apache.org> on 2014/08/05 10:35:11 UTC
[jira] [Updated] (AMQCPP-548) Too many temporary std::string in
Mutex and decaf::lang::Integer::toString(int)
[ https://issues.apache.org/jira/browse/AMQCPP-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Leung updated AMQCPP-548:
--------------------------------
Summary: Too many temporary std::string in Mutex and decaf::lang::Integer::toString(int) (was: Too many std::string copy in decaf::lang::Integer::toString(int))
> Too many temporary std::string in Mutex and decaf::lang::Integer::toString(int)
> --------------------------------------------------------------------------------
>
> Key: AMQCPP-548
> URL: https://issues.apache.org/jira/browse/AMQCPP-548
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Components: Decaf
> Affects Versions: 3.8.2
> Reporter: Jeremy Leung
> Assignee: Timothy Bish
> Attachments: AMQCPP-548.patch
>
>
> Every Mutex will associated with a MutexProperties and the name of the Mutex is actually generated by the DEFAULT_NAME_PREFIX plus a call to Integer::toString( ++id ).
> From the profiling of our application (highly multi-threaded), we found that many times are spent in the std::basic_string allocation and deallocation inside the functions decaf::lang::Integer::toString(int) and decaf::lang::Integer::toString(int, int).
--
This message was sent by Atlassian JIRA
(v6.2#6252)