You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2019/04/22 17:49:00 UTC

[jira] [Commented] (GEODE-6688) InternalDistributedMember could use readInt instead of readInteger

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

Darrel Schneider commented on GEODE-6688:
-----------------------------------------

I have a possible for this in: 

be934f16a90bea9100a91582a7bcde54768c17ba

> 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
>
> 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)