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

Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/09/26 18:04:08 UTC

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

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

Dick Cavender closed GEODE-6688.
--------------------------------

> 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
>             Fix For: 1.10.0
>
>          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
(v8.3.4#803005)