You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2015/07/13 09:55:04 UTC

[jira] [Resolved] (ARIES-1319) Reduce memory allocation in org.apache.aries.blueprint.proxy.Collaborator class

     [ https://issues.apache.org/jira/browse/ARIES-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet resolved ARIES-1319.
------------------------------------
       Resolution: Fixed
    Fix Version/s: blueprint-core-1.4.4

Committing to https://svn.apache.org/repos/asf/aries/trunk ...
	A	blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/proxy/CollaboratorFactory.java
	A	blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/proxy/SingleInterceptorCollaborator.java
	M	blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/BeanRecipe.java
	M	blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/container/ServiceRecipe.java
	M	blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/proxy/Collaborator.java
Committed r1690576


> Reduce memory allocation in org.apache.aries.blueprint.proxy.Collaborator class
> -------------------------------------------------------------------------------
>
>                 Key: ARIES-1319
>                 URL: https://issues.apache.org/jira/browse/ARIES-1319
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.4.2, blueprint-core-1.4.3
>            Reporter: Dmitry Konstantinov
>            Assignee: Guillaume Nodet
>              Labels: perfomance
>             Fix For: blueprint-core-1.4.4
>
>         Attachments: memory_allocation_after_byClass.png, memory_allocation_after_byThread.png, memory_allocation_before_byClass.png, memory_allocation_before_byThread.png
>
>
> In case of intensive usage there is an memory and CPU overhead in org.apache.aries.blueprint.proxy.Collaborator which can be easy eliminated:
> 1) Stack has a thread safety overhead, it can be replaced by ArrayDeque, the stack is used in a single thread
> 2) In case of there are no interceptors - it make sense to not allocate each time a Stack object. The reference can be set to null or a static immutable empty stack value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)