[ 
https://issues.apache.org/jira/browse/GEODE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830480#comment-16830480
 ] 

ASF subversion and git services commented on GEODE-6688:
--------------------------------------------------------

Commit 7fbb95c129f11a528bad02c7a2d5d8222f8e4ca2 in geode's branch 
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7fbb95c ]

GEODE-6688: prevent Integer allocation in InternalDistributedMember 
deserialization (#3514)

InternalDistributedMember now uses readInt instead of readInteger
to prevent an Integer instance creation.


> InternalDistributedMember could use readInt instead of readInteger
> ------------------------------------------------------------------
>
>                 Key: GEODE-6688
>                 URL: https://issues.apache.org/jira/browse/GEODE-6688
>             Project: Geode
>          Issue Type: Improvement
>          Components: serialization
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Minor
>              Labels: performance
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> InternalDistributedMember uses DataSerializer.readInteger in a few places 
> that tend to be called often. If this code instead called DataInput.readInt 
> it would save the allocation of an instance of Integer. Since 
> DataSerializer.readInteger is implemented by calling DataInput.readInt this 
> optimization should not have any issues.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to